Technical Program Manager, OMHS Software, Controls, and Science

This is a delivery-focused role, not a ticket-tracking one. You will own the coordination that gets programs delivered on time, working from a defined strategic goal and a general technical approach. You will turn plans into milestones, dependencies into action plans, and cross-team hand-offs into coordinated delivery. We're deploying new automation technology to fulfillment sites quarterly. Each deployment involves software teams, controls engineers, hardware commissioning, field operations, and vendor coordination converging on a building with a ship date that does not move. Someone needs to keep those pieces moving together toward that date. That someone is you. In our operating model, TPMs are assigned to programs with cross-team dependencies, not to individual products. Product managers own the what and why. Engineering leaders run their own sprints. You step in when delivery requires coordination across team boundaries, and you own the delivery of your program end to end, working closely with a senior TPM or your manager on scope and priorities. You will partner with product managers and engineering leads to plan work, establish milestones, and drive delivery. Your program will have a defined strategic goal and a general technical direction. When ambiguity surfaces during execution, you will resolve what you can and escalate what you cannot so the schedule holds. Impact at scale: The program you deliver will directly affect whether Amazon's next fulfillment buildings launch on time with functioning automation. You will help refine the coordination practices the team uses to scale deployments from a handful of sites to many more. Your work will be visible in buildings that are running, shipping packages, and operating reliably. Key job responsibilities Program Delivery Across Team Boundaries - Own planning, execution, and delivery of a program that spans multiple engineering teams and deployment partners - Partner with product managers and engineering managers to scope work, confirm priorities, and establish quarterly milestones - Track and manage cross-team dependencies, flagging early when a change in one system could affect upstream or downstream systems - Coordinate deployment activities including testing, rollout, and operational readiness for live fulfillment sites Drive Execution Through Complexity - Document program requirements, success metrics, and delivery timelines, and drive the clarity needed when technical details are still open - Manage the schedule, track and mitigate risks early, and keep scope under control - Drive timely decisions, clear the blockers you can, and escalate promptly when the program is at risk - Plan for the unexpected and raise maintainability concerns when delivery pressure could compromise quality Communicate with Clarity and Purpose - Own communications for your program so stakeholders have the right information at the right time - Produce clear documentation: program requirements, risk logs, milestone tracking, and stakeholder updates - Facilitate working discussions that balance business urgency with technical rigor - Present program status and trade-offs to stakeholders and team leadership, and contribute to updates for senior leadership Build Better Delivery Practices - Suggest improvements to how cross-team programs are planned and executed - Incorporate quality and operational excellence improvements into your program plan - Run retrospectives and post-mortems that capture real learnings and follow through on the actions - Support onboarding of new team members and participate in hiring A day in the life Your morning starts checking in on the program you own: a multi-team software integration with a deployment date next quarter. You also help coordinate a hardware-software effort where vendor deliveries are being tracked against commissioning windows. Mid-morning, you're running a dependency sync between two engineering teams whose changes are converging on the same system.