Skip to main content
PProfileMatch

23 open Technical Program Manager jobs

Real, currently-open Technical Program Manager roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Technical Program Manager guide.

Hiring snapshot for Technical Program Manager

The most common locations right now are New York, NY (2), Mountain View, California (HQ) (2), USCA (1). 3 of these 23 roles (13%) list a remote option. 15 were posted in the last two weeks. By team, the biggest groups are Data & AI (7), Engineering (2).

Computed from the 23 open listings shown below.

Guide: working as a Technical Program Manager

Technical program managers coordinate large efforts that span several engineering teams, such as a platform migration or a multi-team launch. They map dependencies, build the schedule, surface risks early, run cross-team syncs and keep leadership informed. Unlike a product manager, they own how and when work lands, not which features to build.

Core skills employers look for

  • Cross-team dependency mapping
  • Program planning and milestones
  • Risk and issue tracking
  • Technical architecture literacy
  • Status reporting to leadership
  • Launch readiness reviews
  • Agile and release processes
  • Negotiating scope and trade-offs

How to stand out when you apply

  • Describe programs by their scope and coordination: which teams and systems were involved, what the critical path was, and how you recovered when a dependency slipped.
  • Show technical depth by explaining how the services in a program you delivered talked to each other, so engineers trust you to spot integration risks early.
  • Bring an anonymised sample artefact, such as a launch checklist, risk register or one-page status update, to show how you communicate under pressure.
  • Engineers moving into TPM work should emphasise times they informally led a cross-team project, including the meetings, docs and decisions they drove.

What the interviews usually cover

Expect a program-management round on running a complex cross-team project, a technical round where you explain or sketch a system at a high level, and behavioural questions about influencing teams you do not manage. Interviewers often pose a scenario, such as a launch at risk because one team is behind, and watch how you weigh options and escalate.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company