About this role.
Playson is seeking a Technical Program Manager to own end-to-end delivery for games, platform work, or product features. The role combines technical delivery leadership with hands-on improvement of engineering and release workflows, including CI/CD, release checks, API integrations, and internal automation. The successful candidate will manage forecasts, identify delivery risks early, enforce release readiness, and align product, engineering, QA, and client-facing stakeholders. This is a delivery-ownership role rather than a coordination-only program management position, reporting directly to the VP of Delivery.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Job Complexity
4/5Pace & Pressure
4/5Autonomy Level
5/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first map the existing workflow and measure where manual handoffs, delays, and errors occur. I would then prioritize the highest-impact issue, automate it with maintainable tooling or API integrations, and track release lead time, failure rate, and stakeholder feedback to validate the improvement.
I use leading indicators such as unstable builds, incomplete test coverage, unresolved dependencies, unclear ownership, repeated environment failures, and unverified rollback plans. I raise the risk early with a clear impact assessment, owner, mitigation plan, and decision deadline.
Release readiness means the build has passed agreed quality gates, critical testing is complete, documentation and operational ownership are in place, dependencies are confirmed, and rollback or incident-response plans are understood. If any material risk is unresolved, I communicate it clearly and recommend whether to delay or proceed.
I would base forecasts on actual throughput, dependency status, team capacity, technical risk, and validated scope rather than optimistic target dates. I would communicate assumptions, confidence levels, and changes promptly so leaders understand both the expected outcome and the risks around it.
I make trade-offs explicit by connecting each option to customer impact, delivery dates, technical risk, and quality requirements. I facilitate a decision with the accountable owners, document the outcome, and ensure the resulting plan has clear responsibilities and checkpoints.
About the role
We’re looking for someone who owns delivery – not tracks it, not reports it, owns it.
You’ll be responsible for a specific area: games, features, or platform work. From the first conversation about a requirement through to production – you’re on the hook for the whole thing.
This isn’t a coordination-only role. We need someone with previous hands-on software engineering, DevOps, release engineering, or similar technical experience who can actively improve and automate the way software is built, tested, and released.
You set the timeline, track it, and communicate changes before people start asking questions. If there’s a blocker, you’ve already seen it. If a release isn’t ready, you say so – clearly and early.
You’ll look at how work flows through your area and fix what’s broken. Not just follow whatever process exists. You’ll design something that actually works, iterate on it, and make it better over time.
A key part of the role will be identifying manual steps, bottlenecks, and failure points in development and release workflows, and then building practical automation to remove them. This may include improving CI/CD pipelines, automating release checks, connecting tools through APIs, and developing scripts or lightweight internal solutions.
Quality is yours too. Not QA’s problem alone, not the tech lead’s problem. You own release readiness: is it tested, is it documented, does anyone know the operational risk. If the answer is no, it doesn’t ship.
You’ll work closely with product, engineering, QA, and client-facing teams, keep them aligned, and report directly to the VP of Delivery.
What we expect from you
First 30 days
Understand how delivery actually works in your area – not how it should work, how it actually works
Map where work gets stuck, what the recurring blockers are, and who the key people are
Meet everyone who matters: product owners, tech leads, QA, release managers, client teams
Write up what you found and share it with the VP of Delivery
First 60 days
Take ownership of delivery tracking for your area
Pick the biggest workflow problem you found and start fixing it
Show you can catch a blocker before it causes a delay – at least twice
First 90 days
Own and communicate a delivery forecast that stakeholders actually trust
Ship at least one release with no last-minute surprises – quality gates passed, documentation done, everyone aligned
Present your view on how delivery should work in your area going forward
What we’re looking for
3+ years in an engineering delivery, software delivery leadership, or similar role where you owned outcomes, not just process
Previous hands-on experience as a Software Engineer, DevOps Engineer, Release Engineer, Build Engineer, Developer Productivity Engineer, or in a similarly technical role.
Strong understanding of the software development lifecycle, including builds, automated testing, versioning, deployment, monitoring, and rollback.
You catch problems early. Not because you’re lucky, but because you know what signals to watch
You’ve worked across engineering, product, and QA and you know how to keep them moving together
Strong communicator – you can give a clear, honest delivery update to a VP without needing a slide deck
You care about quality beyond closing tickets – release readiness, testing coverage, operational risk are things you think about naturally
You’re genuinely interested in the product you’re delivering, not just the process around it
You actively look for repetitive manual work and replace it with reliable, maintainable automation.
Nice to have
Background in iGaming, gaming, or another regulated product environment
Experience in a B2B or multi-operator delivery model
Familiarity with incident management and post-mortems
Experience working with external studios or third-party development partners
OKR-based planning and how it connects to delivery cadence
Jira or similar tooling – configuration, not just usage
What We Offer
Competitive Salary
Quarterly Bonuses
Unlimited Paid Time Off
Unlimited Paid Sick Leave
Remote & Flexible Working
Private Medical Insurance
Financial Support for Life Events
Professional Development Budget
International Exposure
Regular Company Events
*Benefits may vary depending on location and contractual agreement
By submitting your application, you acknowledge that your personal data will be processed in accordance with our Privacy Policy.
#LI-DNI
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
Upload your resume now
- To unlock remote work opportunities and be discovered by global employers.
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
