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
Wh
