A technical program manager (TPM) leads work that spans several engineering teams and has to land on one date. If you're weighing the job, hiring for it or trying to explain it to your manager, this guide covers what a TPM does, how it differs from the roles around it, what employers ask for at each level, what the job pays and how people get into it. If you're new to the role itself, our guide to what a program manager is covers the basics first.
- A TPM owns the plan, schedule, risks and dependencies of a technical program that crosses teams, and gets results through influence because the engineers don't report to them.
- Google's postings ask for a bachelor's degree in a technical field (or equivalent practical experience) and 2 years of program management at mid level, rising to 8 years at senior level. Amazon's postings for senior and principal roles ask for 5 to 10+ years, plus years of working directly with engineering teams.
- Pay depends heavily on the source. Google posts a base range of $138,000 to $278,000 across the levels we read, and Levels.fyi reports a US median total compensation of $244,500 from 1,497 submissions.
- Most people arrive from engineering, or from program or product management with enough technical depth to challenge an estimate.
- US median total pay, Levels.fyi
- $244,500
- salary submissions behind it
- 1,497
- Google job matches on 19 Oct 2026
- 314
What Is a Technical Program Manager?
A technical program manager is the person who plans and drives a technical program from start to finish across several teams. Google's own job description says a TPM uses technical expertise to lead complex, multi-disciplinary projects from start to finish, working with stakeholders to plan requirements, identify risks and manage schedules. The Digital Project Manager puts it more briefly: TPMs oversee technical project delivery.
The word "program" matters, though it's easy to skim past. A project has one goal and one team. A program groups related projects that have to deliver together, so most of a TPM's work sits in the gaps between teams: one team's output is another team's input, and a slip in either one moves the launch date. If you'd like the general version of that distinction, our guide to program manager vs project manager covers it.
The word "technical" matters just as much, and it's the part people argue about. AIM Consulting says TPMs usually begin as software engineers and move into the role if they prefer working with people over code. The Digital Project Manager describes the test a little differently: a program manager knows enough to push back on a flawed engineering estimate, while a TPM can debate architecture decisions with the engineering team.
What Does a Technical Program Manager Do?
A TPM spends the week on five things: turning a goal into requirements and milestones, tracking the dependencies between teams, spotting risks early, keeping stakeholders informed and unblocking whatever is stuck. The postings we read describe the same pattern at different scales, and here's how it breaks down.
| Part of the job | What it looks like in practice | Source |
|---|---|---|
| Plan | Define requirements and own end-to-end technical execution for a program | Google, TPM II posting, Data Center and Logistics Analytics |
| Schedule and dependencies | Drive timelines, proactively manage constraints, identify dependencies and keep schedules and critical-path items aligned | Google TPM posting, AI2 TPU Software |
| Risk | Manage scope, resource planning, risk and roadmap delivery for complex infrastructure | Google TPM posting, AI2 TPU Software |
| Communication | Give clear updates and recommendations to leadership and executive stakeholders | Google TPM posting, AI2 TPU Software |
| Technical judgment | Take part in architecture conversations and anticipate the consequences of design decisions | AIM Consulting |
| Delivery quality | Cover non-functional areas such as telemetry, performance, reliability, security and compliance | AIM Consulting |
The domain changes a lot between employers, which is why a salary or a skills list can mislead. The first page of Google's results for the title on 19 October 2026 included roles in data center development, data center networking, AI model launches at DeepMind, Pixel devices, TPU software and security. The title is the same, but it's different work: a hardware program (supplier dates, manufacturing builds) isn't a software launch (release trains, feature flags). When you read a TPM posting, check which kind of program it is.
The Digital Project Manager groups the duties into technical, leadership and business work. The technical part includes leading design and architecture discussions and managing through agile methods such as Scrum. The leadership part is acting as the liaison between technical and non-technical audiences. The business part includes meeting objectives within the time and budget and influencing people without direct authority.
What a TPM owns, and what they don't
A TPM gets blamed for things they don't control, yet gets overlooked for things they do. This table is our own working split, not a standard. Adjust it with your engineering and product leads before the program starts, since they'll have views.
| Decision or artifact | TPM role | Who usually decides |
|---|---|---|
| Program plan, milestones and critical path | Owns | TPM, with sign-off from the sponsor |
| Dependencies between teams | Owns the register and the follow-up | Each team owns its side of the dependency |
| Risk and issue log | Owns | Risk owners decide the response |
| Technical design and architecture | Challenges and asks for trade-offs | Engineering lead or architect |
| Product scope and priorities | Surfaces the cost of changes | Product manager |
| Staffing and performance | Informs | Engineering managers |
| Status and escalations | Owns | TPM raises, the sponsor decides |
For the risk and issue side, the RAID log guide shows a program-level example, and the RACI chart guide covers who is accountable for what.
TPM vs Program Manager, Project Manager, Product Manager and Engineering Manager
A TPM differs from its neighbors in what it owns and how technical it has to be. Here's the short version. The Digital Project Manager says a TPM brings a higher degree of technical knowledge than a program manager. A Substack essay by Malvika Souran (January 2026) says TPMs don't typically own the product vision or customer roadmap, and, unlike engineering managers, don't own people management or code quality. So the TPM owns execution across both.
| Role | Main question it answers | Owns | Technical depth expected |
|---|---|---|---|
| Technical program manager | How do these teams deliver together, and when? | Plan, dependencies, risks, status across teams | High: can discuss architecture and trade-offs |
| Program manager | How do these projects add up to the business outcome? | Program scope, benefits, governance | Enough to challenge estimates |
| Project manager | How do we deliver this one project on time and on budget? | One project's schedule, budget, team tasks | Varies by project |
| Product manager | What should we build and why? | Product vision, roadmap, requirements | Medium to high, depending on the product |
| Engineering manager | How do we grow the team and keep quality high? | People, hiring, code quality | High |
Technical program manager vs technical project manager
The overlap with the technical project manager is the one that confuses candidates most, and it's rarely explained. None of the explainers we read define the split, so this is our reading: a technical project manager runs one technical project with one schedule and usually one team, and a TPM runs the program that several such projects belong to. Levels.fyi lists the technical project manager as a separate title with a US median total pay of $163,500, against $244,500 for the TPM, which suggests employers do treat them differently. Titles still vary by company, of course, so compare the responsibilities in the posting, not just the name.
Technical program manager vs product manager
A product manager decides what gets built and why, and the TPM makes sure it gets built across the teams involved. AIM Consulting says product managers help create the vision for products and drive feature prioritization, while TPMs are in charge of delivery for one or more technical projects, from idea through deployment. It also notes that how technical a TPM is varies: a TPM nearer the business side works differently from one who gets heavily involved in engineering.
What Do Employers Ask For at Each Level?
Employers ask for a technical bachelor's degree or equivalent experience, plus years of program management that rise with the level. The table below comes from postings we read on 19 October 2026. It's a small sample from two employers, not an industry average, so don't read it as a rule.
| Posting | Level label | Degree | Years asked for | Other requirement |
|---|---|---|---|---|
| Google, TPM II, Data Center and Logistics Analytics | Mid | Technical bachelor's or equivalent practical experience | 2 years in program management | Supply chain experience and data analytics experience |
| Google, TPM, AI2 TPU Software | Advanced | Technical bachelor's or equivalent practical experience | 8 years in program management | Experience with AI or machine learning projects, tools or infrastructure |
| Google, Senior TPM, Pixel Devices | Advanced | Technical bachelor's or equivalent practical experience | 8 years in program management | None in the minimum list |
| Amazon, TPM III, Seattle | Not stated | Not stated in the part we read | 5+ years in technical product or program management, 7+ years working directly with engineering teams | 3+ years of software development experience |
| Amazon, Sr. TPM, Bellevue | Senior | Not stated in the part we read | 5+ years in technical product or program management, 7+ years working with engineering teams | 5+ years of TPM work directly with software engineering teams |
| Amazon, Principal TPM, Austin | Principal | Not stated in the part we read | 10+ years of technical product or program management, 10+ years working with engineering teams | 5+ years of manufacturing experience |
Two patterns stand out, and they're worth knowing before you apply. First, "equivalent practical experience" appears in every Google posting we read, so the degree isn't a hard gate there. Second, Amazon asks for years of working directly with engineering teams as a separate requirement from program management years, and in the TPM III posting it asks for software development experience too. That clearly signals how much technical depth a TPM is expected to have, even though the degree is flexible.
How Much Does a Technical Program Manager Make?
A technical program manager at Google earns a posted base of $138,000 to $278,000 in the roles we read, and the Levels.fyi US median total compensation for TPMs is $244,500. The numbers differ because they measure different things, so read the table before you compare them. You'll see why a single "average" is misleading.
| Source | What it measures | Figure | Date |
|---|---|---|---|
| Google TPM II posting | Posted US base range, plus 15% bonus target, equity and benefits | $138,000 to $197,000 | 19 Oct 2026 |
| Google Senior TPM and AI2 TPU Software postings | Posted US base range, plus 20% bonus target, equity and benefits | $192,000 to $278,000 | 19 Oct 2026 |
| Levels.fyi | Total compensation (base, annualized stock, bonus), US, 1,497 submissions | Median $244,500; 25th percentile $185,000; 75th $310,000; 90th $390,000 | Updated October 2026 |
| The Digital Project Manager | Average range, source not stated | $130,000 to $210,000 | Updated May 2025 |
| BLS, project management specialists | Median annual wage for a related occupation | $102,320 | May 2025 |
| BLS, computer and information systems managers | Median annual wage for a related occupation | $175,140 | May 2025 |
BLS doesn't publish a TPM category, so the last two rows bracket the role from below and above rather than measure it. Project management specialists is the closer match for the coordination work, and computer and information systems managers for the technical seniority. BLS projects 7% employment growth for project management specialists from 2025 to 2035, against 3% for all occupations.
Levels.fyi also lists the highest-paying employers by US median total compensation: Meta at $388,000, Nvidia at $350,000, Google at $338,000, LinkedIn at $325,000 and Oracle at $290,000. Those are submissions from people at large technology employers, so treat them as the top of the market. They aren't what a typical TPM earns, although they show how far the ceiling goes. Location moves the number as well: the same page puts the Atlanta area at $224,500, Greater Boston at $219,450 and the New York area at $207,000.
In a salary context, "TPM" means technical program manager, and that's how salary sites list it. For a negotiation, use the employer's posted range when there is one, the Levels.fyi percentiles for the market, and your level's years-of-experience bar from the table above.
How to Become a Technical Program Manager
Most people become a TPM by adding program management experience to an engineering background, or by adding technical depth to a program or product management background. The steps below are our suggestion, built from what the postings and the two explainer pages ask for.
Choose your route in
AIM Consulting says TPMs typically start as software engineers who prefer working with people to writing code. The Digital Project Manager describes the role as a natural next step for program and product managers who have technical expertise. Decide which side you're coming from, because it tells you which gap you'll need to close.
Build technical depth you can show
AIM Consulting describes a spectrum, from understanding architecture trade-offs to digging into code, logs and system documentation. Pick a domain from the postings (infrastructure, devices, AI platforms, security) and learn how its systems fail, so you can ask the right questions in a design review.
Run a cross-team program, even a small one
Postings ask for years of program management, and Amazon separates that from years of working directly with engineers. Volunteer to own a launch that needs three teams, and keep the plan, the dependency list and the risk log yourself. Don't wait for the title.
Learn the artifacts
A RAID log, a RACI chart, a milestone plan and a weekly status report are the working documents of the job. Use our RAID log guide and RACI chart guide to practice on a real program, and our guide to the risk register for the risk side of the plan.
Aim at the right level
Use the levels table above. It's a rough guide, but at 2 years of program management you're looking at mid-level postings, and at 8 you can read senior ones. Count the years of working with engineering teams too, because Amazon asks for them separately.
Prepare for the interview
You'll want to practice the three kinds of question in the next section, with one story for each: a hard dependency, a failing project and a technical trade-off you influenced.
Certifications aren't a requirement in any posting we read. Still, they're not worthless. BLS says certification may help project management specialists but isn't always required, and names none, so treat a PMP or similar credential as optional unless a specific posting asks for one. It's outright wrong to assume you need one.
What to Expect in a TPM Interview
TPM interviews test three things: technical judgment, program management judgment and how you communicate. The Digital Project Manager lists example questions that fall into those groups.
- Technical judgment. Describe a time you made a decision that affected a system's architecture, walk through designing an e-commerce platform, or explain how you'd update more than 10,000 servers without affecting customers.
- Program judgment. Explain how you'd kick off a project, define milestones and communicate them, identify and mitigate risk, or respond when a project is failing or won't meet its deadline.
- Communication. Show how you would turn all of that into something a sponsor can act on, in a few sentences.
The Digital Project Manager says the expectations depend on the seniority of the role and the size of the organization. Bring examples that show your technical knowledge, decisions and problem solving. For the program part, a filled-in plan and risk log from a real program beats a description of your method.
Is Being a TPM Stressful?
Being a TPM can be stressful, but the reasons are structural, and they're fixable. None of the sources we read measured TPM stress, so this is our reading of the role, not a statistic. The postings describe giving updates to executives, holding schedules and critical paths, and chasing dependencies. The Digital Project Manager adds that TPMs often have to get outcomes without direct reporting authority.
That combination is where the pressure comes from, while the workload itself is rarely the issue: you're accountable for a date that depends on people who don't report to you. What helps is making the exposure visible early, and that's mostly bookkeeping. A named owner for every dependency, a risk log that gets reviewed on a schedule and a clear escalation threshold turn "I'm worried about the launch" into a list someone can act on. If the work still feels permanently stressful, check whether you actually own the decisions in the table above or only the blame.
Tools and Documents a TPM Uses
A TPM's tools are mostly the ones the engineering teams already use, plus a handful of documents that sit across them. In practice that means 
Jira for engineering work, 
Asana or a similar tool where product, marketing or operations teams plan, and a place for the program-level documents: the plan, the RAID log, the RACI chart, the decision log and the weekly status.
The hard part's the layer between those tools. A dependency that crosses from a Jira epic to an Asana project isn't visible in either one, and that's where programs slip. For a comparison of the tools that can hold the program level, see our roundup of the best program management software.
The Program Manager is built for that gap. It maps dependencies across Jira and Asana, watches milestones for risk and keeps blockers and decisions in one graph. It doesn't replace your engineering tools, and it's invite-only for signup right now.
A one-page program brief to start every program
This is our own template. Fill it in during the first week and keep it next to the plan. It's one page on purpose.
- Goal and launch date written in one sentence, agreed with the sponsor
- Every team involved, with one named contact each
- Milestones with the team that owns each one
- Dependencies between teams, each with an owner and a needed-by date
- Top five risks with an owner and a review date
- Decision rights written down: who decides scope, design, staffing and the launch date
- Escalation threshold: how late or how large before it goes to the sponsor
- Status report format and the day it goes out
FAQ
What is a technical program manager?
A technical program manager plans and drives technical programs that cross several teams, owning the schedule, dependencies, risks and status. The role needs enough technical depth to take part in architecture discussions and challenge engineering estimates.
How much do TPMs make?
TPMs make a US median total compensation of $244,500, according to Levels.fyi from 1,497 submissions, with a 25th to 75th percentile range of $185,000 to $310,000. Google's posted base ranges for the roles we read were $138,000 to $197,000 at mid level and $192,000 to $278,000 at senior level, before bonus and equity.
What does TPM mean in a salary context?
It means technical program manager. Salary sites such as Levels.fyi list total compensation for the title, which includes base pay, annualized stock and bonus.
Is TPM a stressful job?
Being a TPM can be stressful, because you're accountable for dates that depend on teams that don't report to you. No source we read measures TPM stress, but clear dependency ownership, a regularly reviewed risk log and an agreed escalation threshold remove much of the pressure.
Do technical program managers need to code?
Technical program managers don't necessarily need to code. AIM Consulting describes a spectrum of technical depth, from understanding architecture trade-offs to working with code, logs and configuration. Amazon's TPM III posting asks for 3+ years of software development experience, so check what the posting for your level wants.
Do you need a degree to become a TPM?
Google's postings we read ask for a bachelor's degree in a technical field or equivalent practical experience, so experience can substitute. BLS lists a bachelor's degree as the typical entry-level education for project management specialists.
Leave a Reply