Technical Program Manager Jobs

101 open technical program manager jobs at 40 employers, updated twice a day.

101 Open roles
40 Companies hiring
16 Cities

The newest technical program manager jobs

See all 101 technical program manager jobs

Technical program manager jobs by city

The market for technical program manager roles

As of 23 September, 83 technical program manager roles are open at 40 employers. 14 new roles have been posted since 21 September. The countries with the most are the United States, the United Kingdom and India. Of the roles that say how they work, 41% are remote or hybrid.

Technical program managers listed on the board are concentrated heavily in the United States, which accounts for about two thirds of all postings. The United Kingdom and India together make up roughly a fifth of the remainder, with smaller numbers across Canada, Singapore, South Korea and several European countries. Most openings are at mid-level, with senior roles accounting for about a third and lead-level positions making up most of the rest; junior openings are rare. Posting dates are spread across recent weeks, with a meaningful share of roles having been listed within the past week, though a notable proportion are older than a month. About two in five roles on the board sit with just five employers, suggesting a degree of concentration. There is not enough weekly history yet to describe any trend over time.

How recently the open roles were posted

This week 14
Last week 11
Two weeks ago 7
Three weeks ago 11
One to two months ago 14
Two to three months ago 8
Earlier 18

Figures are measured every Monday.

About technical program manager roles

A technical program manager sits between engineering leadership and project delivery. Unlike a product manager, who owns the what and why of a product, or a traditional project manager, who may focus on scope, schedule and budget without deep technical involvement, the TPM is expected to understand system architecture, surface dependencies and technical risks, and translate those constraints into programme plans that engineering teams can execute. The role spans multiple teams or organisations rather than a single squad. People enter from software engineering, engineering management or from programme management backgrounds where they have built up technical depth. Progression tends to run from driving single complex programmes toward coordinating large portfolios, with some frameworks placing TPMs on individual-contributor tracks rather than management tracks.

Skills and experience employers ask for

LLMs, agents and evaluation appear in roughly a third of descriptions on the board, pointing to significant demand for TPMs who can operate in AI and machine learning contexts. APIs, cloud platforms such as Azure and AWS, and data tools including SQL and Python appear in a meaningful minority of descriptions. A/B testing and GPU infrastructure also appear, suggesting some roles sit close to model development and experimentation pipelines. These are skills mentioned in postings, not stated requirements.

LLMs 31%
Agents 29%
Evaluation 29%
APIs 17%
Master's degree 15%
SQL 12%
Python 11%
Azure 11%
GPUs 10%
AWS 8%
A/B testing 8%
Go 7%

Share of the open roles' descriptions that mention it, from a sample of 83. A mention is not a requirement.

Where the technical program manager roles are

United States 55
United Kingdom 8
India 7
Canada 3
Singapore 2
South Korea 2
Spain 1
France 1
Taiwan 1
Germany 1

The most active employers for technical program manager roles

Office, hybrid or remote?

Among roles on the board that state a work arrangement, on-site is clearly the most common, accounting for well over half. Hybrid roles make up about a quarter to a third of those stating a mode, and fully remote positions are a small minority. This profile suggests most hiring organisations expect TPMs to be physically present with their engineering teams for most or all of the working week.

Getting a technical program manager role

  1. Show cross-team coordination in examples TPM interviews typically probe how you have aligned multiple engineering teams toward shared deliverables. Prepare specific examples that cover dependency mapping, risk identification and stakeholder communication rather than single-team project stories.
  2. Build visible technical depth Employers distinguish TPMs from general project managers by expecting architectural understanding. Being able to explain a system's technical constraints to both engineers and non-technical partners is a skill worth evidencing explicitly in your application materials.
  3. Engage with AI and ML programme patterns A large share of descriptions on the board mention LLMs, agents and model evaluation, so familiarity with how AI development programmes are structured — including how experimentation and deployment cycles differ from traditional software delivery — is increasingly useful for this cohort of roles.
  4. Understand programme management credentials PMI's PMP and PgMP certifications are recognised in the field; the PgMP in particular is oriented toward coordinating several related projects toward organisational goals, which maps closely to how the TPM role is described by employers. Understanding what each covers helps you speak to interviewers who use that vocabulary.

Questions about technical program manager jobs

A project manager typically focuses on scope, schedule and budget for a defined piece of work. A technical program manager is expected to understand system architecture and engineering trade-offs well enough to identify dependencies and technical risks across several teams, and to translate those into programme plans — not just track milestones.

A product manager owns the direction and priorities of a product. A technical program manager focuses on coordinating the engineering delivery of that work across teams, managing schedules, dependencies and risks rather than deciding what gets built or why.

It varies by employer. Some organisations, such as Dropbox in its published career framework, place TPMs on individual-contributor tracks rather than people-management tracks. In that model, seniority is measured by the scope and complexity of the programmes driven rather than by the size of a reporting team.

People typically enter from software engineering backgrounds who move toward coordination and delivery, or from programme and project management roles where they have progressively taken on more technical responsibility. Both paths are recognised by employers who publish guidance on the role.

Based on published employer guidance, TPM interviews commonly cover programme management, stakeholder management and behavioural questions. At technically focused employers, at least one software system design question is also expected alongside the programme management content.