Technical Program Manager

About the role

The role centers on owning delivery end to end for a specific area such as games, features, or platform work. From the first conversation about a requirement through to production, you are on the hook for the entire outcome. This is not a coordination-only position; it requires someone with previous hands-on software engineering, DevOps, release engineering, or similar technical experience who can actively improve and automate how software is built, tested, and released. You set the timeline, track it, and communicate changes before people start asking questions. When there is a blocker, you have already seen it. If a release is not ready, you say so clearly and early. You will look at how work flows through your area and fix what is broken, designing something that actually works, iterating on it, and making 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, which may include improving CI/CD pipelines, automating release checks, connecting tools through APIs, and developing scripts or lightweight internal solutions. Quality is also your responsibility, not just QA's problem or the tech lead's problem; you own release readiness, including whether it is tested, documented, and whether anyone understands the operational risk, and if the answer is no, the release does not ship. You will work closely with product, engineering, QA, and client-facing teams, keep them aligned, and report directly to the VP of Delivery.

Key facts

What you'll do

Understand how delivery actually works in your area, not how it should work, and document the real workflow, decisions, and outcomes.

Map where work gets stuck, what the recurring blockers are, and who the key people are for your area of responsibility.

Meet everyone who matters, including product owners, tech leads, QA, release managers, and client teams, to build shared context and trust.

Write up what you found about current delivery behavior and share it with the VP of Delivery to drive alignment.

Take ownership of delivery tracking for your area, including status, risks, and forecasts that stakeholders can rely on.

Pick the biggest workflow problem you identified in your first weeks and start fixing it with practical, incremental improvements.

Show you can catch a blocker before it causes a delay, demonstrating this at least twice through early warnings and clear communication.

Own and communicate a delivery forecast that stakeholders actually trust, using real data and transparent assumptions.

Ship at least one release with no last-minute surprises, ensuring quality gates are passed, documentation is complete, and everyone is aligned.

Design and iteratively improve how delivery works in your area, replacing outdated steps with something that actually works.

Identify manual steps, bottlenecks, and failure points in development and release workflows, then build practical automation to remove them.

Improve CI/CD pipelines, automate release checks, connect tools through APIs, and develop scripts or lightweight internal solutions where needed.

Take responsibility for release readiness, including testing coverage, documentation quality, and operational risk, and ensure no release ships if the answer is no.

Work closely with product, engineering, QA, and client-facing teams to keep them aligned and remove cross-team dependencies.

Communicate clear, honest delivery updates to leadership, including the VP of Delivery, without needing a slide deck to explain the status.

Present your view on how delivery should work in your area going forward, backed by evidence from the problems you solved and the data you collected.

Requirements

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 are lucky, but because you know what signals to watch and where to look.

You have worked across engineering, product, and QA and you know how to keep them moving together without friction.

Strong communicator who can give a clear, honest delivery update to a VP without needing a slide deck or extra packaging.

You care about quality beyond closing tickets, including release readiness, testing coverage, and operational risk, and these are things you think about naturally.

You are genuinely interested in the product you are delivering, not just the process around it, and you bring curiosity and ownership to the product outcomes.

You actively look for repetitive manual work and replace it with reliable, maintainable automation that reduces risk and saves time.

You are comfortable making decisions, setting timelines, and communicating changes proactively so that stakeholders are never surprised.

You take end-to-end responsibility for specific areas and ensure that what you own reaches production reliably and predictably.

You can operate independently with minimal supervision while collaborating closely with cross-functional partners.

You communicate in a direct, factual, and constructive manner, even when delivering difficult news about delivery or quality.

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, to optimize workflows for your area.

Practical notes

This role is full time.

The position is based in the European Union.

Candidates must be eligible to work in the European Union without sponsorship.

No specific hours, travel, visa, or deadlines are stated in the original source.