What you'll be expected to do
What they're grading- Run programs that span several engineering teams, from kickoff and goals to launch
- Find the technical dependencies and risks between teams, and plan around them early
- Set milestones, track progress and report status upward without surprises
- Hold design conversations with engineers: trade-offs, limits, what scales and what doesn't
- Get buy-in from teams you don't manage, and resolve conflicts between their goals
- Define how the program measures success, and use the numbers to make calls
What does the interview loop look like?
7 rounds · 4–8 weeksMost companies follow a similar pattern for TPM interviews. Total calendar time is 4–8 weeks from recruiter screen to offer.
Background, level, and which kind of TPM role: software, infrastructure, hardware or AI programs
Half behavioural and situational, half technical, per Amazon's published process
What they're scoring
- Specific programs you ran, with your own decisions
- Comfort talking about the systems behind them
Amazon asks you to write about your most innovative project or a time you simplified customers' lives, and interviewers may discuss it
What they're scoring
- Clear writing
- Decisions backed by data
A real program end to end: complexity, strategy, prioritisation, execution, risk, ambiguity, communication
What they're scoring
- Concrete examples, never theory
- Risks found early and mitigated
Amazon: at least one software systems design question. Meta: a solution design round on product clarity, technical design, metrics and trade-offs
What they're scoring
- Broad design knowledge and depth in one area
- Metrics tied to the design
A deep dive on a past program's architecture, dependencies and trade-offs, and how you troubleshot it. Meta says you won't write code
What they're scoring
- End-to-end understanding of the system
- Trade-offs discussed as they come up
Influencing without authority with a cross-functional partner; conflict, growth, ambiguity, results and communication
What they're scoring
- Buy-in won from resistant teams
- Communication tailored to leadership
TPM runs 7 rounds. See where every role lands in the 2026 Tech Interview Report.
Sample questions you should be ready for
9 of the ones that decide itRepresentative of what companies ask at this level. Every question here can be practised out loud, which is the fastest way to find out whether your answer holds up under follow-ups. Calibrd adds voice practice with coaching on every answer, and a full voice mock interview: a live round with an AI interviewer who has read the role and your CV, then an honest debrief.
- 01“Design a live streaming service that holds up when a celebrity starts a stream.”
- 02“Design a reservation system for hotels or tickets, then plan the program to build it across four teams.”
- 03“Walk me through the architecture of a program you ran: the components, the dependencies and the trade-off you'd change.”
- 04“Walk us through how you create a strategy and roadmap for a program.”
- 05“Which metrics do you use to review a program's success? Give a real example.”
- 06“How do your responsibilities differ from a project manager's?”
- 07“Tell me about a time another engineering team's goals conflicted with yours and would have blocked your program. What did you do?”
- 08“Describe a time you couldn't meet a deadline. How did you communicate it, and to whom?”
- 09“Tell me about a time you pushed back on your engineering lead.”
These are the general ones. Paste a real posting and Calibrd predicts the questions that company asks for that exact role, then interviews you on them.
Predict my questions →Compensation benchmark
US majors · USD · medianTypical pay for TPM at major US tech companies, headline numbers in USD. Typical pay in London, Berlin and Singapore is meaningfully lower, and equity varies a lot by company stage.
Levels.fyi medians for TPMs in the United States, read 13 October 2026: Google $397K, Meta $388K, Amazon $281K, Microsoft $252K total a year; $244K across all companies. At Amazon, Levels.fyi puts TPM L6 (senior) at about $286K and L7 (principal) at about $474K.
How to prep
6 tactical tipsLead behavioural answers with the STAR method: Situation, Task, Action, Result. The tips below build on that structure for this specific role.
- Read Amazon's TPM prep page and Meta's TPM guide even if you aren't applying there: they are the only two published rubrics, and other companies test the same things
- Prepare two programs you ran end to end: the goal, the teams, the dependencies, the biggest risk and how you handled it, with numbers
- Practise one system design out loud at the level Amazon describes: broad knowledge, with depth in one area you know well
- Prepare a technical retrospective of one past program: the architecture, the trade-offs as they came up, and one problem you troubleshot
- For Amazon, write a one-page account of your most innovative project before the writing assessment arrives
- Prepare stories for conflict between teams, a missed deadline, and pushing back on an engineering lead
Where do TPM candidates fail?
Spot it in a mock firstA few common mistakes that get TPM candidates rejected even when they are otherwise strong. Worth catching in a mock interview before they show up in a real one.
Describing a program by its timeline and meetings, and going vague when the interviewer asks how the system worked.
Why it fails
Meta's guide says TPMs aren't crisis managers or communication facilitators; they dive deep into system design and architecture. Candidates report being told they'd be better suited to a non-technical PM role after exactly this.
Fix
For each program story, know the architecture well enough to draw it: the main components, where they depended on each other, and the trade-off you'd revisit.
Answering a program sense question with a framework (assess impact, mitigate risk) and no real example.
Why it fails
Meta's guide says to avoid theoretical answers and that interviewers will redirect you to a concrete example. Amazon asks for decisions you personally made, with metrics.
Fix
Answer with one real program: what you saw, what you decided, what changed, and a number that shows it.
Saying 'we' throughout, so the interviewer can't tell what you did versus the engineers.
Why it fails
Amazon's guide says 'I' is better than 'we', and asks you to talk about the scope and how you delivered the result as well as how the system works.
Fix
In each story, name your own decisions and actions explicitly, and give the engineers credit for theirs.
Recommended resources
No affiliate linksBooks, courses, and tools that come up most often in TPM prep.
- 01Amazon, Technical Program Manager interview prep →
The full published loop: the phone screen, the writing assessment, five 55-minute interviews and the system design expectation.
- 02Meta, TPM onsite interview prep →
Meta's TPM guide: the five rounds and their rubrics, and how senior and staff answers differ.
- 03Google Careers, how we hire →
Google publishes no TPM-specific guide; its general process applies.
Frequently asked questions
How technical does a Technical Program Manager interview get?
Technical enough to hold a design conversation with engineers, without writing production code. Amazon's TPM loop includes at least one software systems design question and looks for broad design knowledge with depth in one area; Meta runs a solution design round and a technical retrospective with an engineer, where it says you won't write code. Amazon's own guidance says a product manager role, unlike a TPM, does not need to go deep into system design.
How long should I prep before my TPM onsite?
The process takes 4–8 weeks. Spend most of your prep on two program stories you can take apart technically, then one system design out loud, then the behavioural stories.
What's the most common mistake candidates make at the TPM bar?
Sounding like a project manager: timelines, meetings and status, with no depth on the system. Candidates report being told they'd suit a non-technical PM role after exactly this.
What if my interview process is different from what's listed?
TPM loops vary most in how technical the design round is. Amazon includes at least one software systems design question and a writing assessment, and Meta adds a technical retrospective with an engineer. Candidates report that some hardware and data centre teams talk design through verbally or skip it, and that some companies ask for a slide deck presented to a panel. Ask the recruiter on the screening call which rounds you have and how technical they go.
How does this guide compare to running a free scan?
This guide covers the general bar at L5–L6 / IC4–IC5. The free scan reads one real posting and opens the report right here: the questions that role and company will ask, a pay benchmark matched to the level and, with your CV, the gaps an interviewer will probe and a CV score. No account or email first; the report is on screen in about a minute.
Walk in ready
Walk into your TPM interview ready.
Paste your actual job and Calibrd predicts what that company asks for this role, where your CV is thin, and what it should pay. Then rehearse the round out loud with honest feedback until you're confident. Free to start.
Not interviewing yet? See if your CV would make the shortlist for a TPM role →
Free to start · No card · Encrypted at rest, never used to train AI, remove anytime