TechnicalProgramManager

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 meeting-facilitation job. It's not about keeping Jira up to date or running standups. It's about making sure engineering teams have a clear path to delivery and nothing is getting in their way. 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. 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 p