Overview:We are looking for a Senior Technical Program Manager to own the end-to-end delivery of a complex, cross-functional product workstream. You will operate at the intersection of product, engineering, and stakeholder management, translating strategic priorities into executable plans, removing blockers, and ensuring high-quality delivery at pace.This is not a coordination role. You will drive programs with ambiguity, make judgment calls under pressure, and hold engineering and QA teams accountable to outcomes, not just timelines.RequirementsEnd-to-end program ownership for an assigned product workstream: from requirements alignment through release and post-launch reviewCross-functional delivery coordination across Engineering, Project Managers, QA, Design, Business Analysis, and DevOpsDependency mapping, risk identification, and proactive mitigation across workstreamsStakeholder communication: translating technical progress into clear, decision-ready updates for product and business leadershiRelease governance: owning go/no-go readiness, release criteria, and deployment coordinationEscalation management: surfacing blockers early, driving resolution, and maintaining delivery momentumProgram health reporting via Azure DevOps and Jira: sprint tracking, velocity analysis, milestone burn-downContributing to process improvement across the delivery functionWhat You Bring Proven track record owning complex, multi-team technical programs end-to-end in a senior capacityStrong technical fluency: able to engage meaningfully with engineering teams on architecture decisions, technical debt trade-offs, and integration risks without needing to write codeExperience operating in regulated, compliance-sensitive, or enterprise environmentsMastery of delivery frameworks: Agile/Scrum, Kanban, and hybrid models applied pragmaticallyHands-on experience with Azure DevOps and/or Jira at a program level, not just task trackingExceptional stakeholder management skills: able to navigate competing priorities, manage up, and align cross-functional teams without formal authorityStrong written and verbal communication: comfortable producing exec-level updates and technical documentation equally wellComfort operating in ambiguity and making decisions with incomplete informationWhat Success Looks Like in Year One Your workstream ships on time, within scope, with documented quality gates metStakeholders receive proactive updates/reports: surprises are rare, escalations are controlledEngineering and QA teams describe you as a force multiplier, not an overheadYou've identified and resolved systemic delivery risks before they became incidentsYour program documentation and audit trail are clean and referenceable