Loading...
Please sign in to view your progress
TPM interviews: program sense, execution, risk and technical depth. Train with Coach Elena, then take a mock with Marcus.
| # | Name | ||
|---|---|---|---|
1 | The TPM Role and the Loop Document | ||
2 | ![]() | What does a TPM own that a PM doesn't, how does the loop run, and how is it scored? Sit
at a launch table in Elena's 3D lab, spot the conflicts, see how Google grades TPMs and
what changed this year, then practise your ninety-second intro and an ownership story
while Elena presses with the follow-ups real interviewers use.
| |
3 | Program Sense Document | ||
4 | ![]() | Turn a vague goal into a program you could run on Monday. With Elena, plan Wi-Fi for
sixty schools in a 3D program lab: ask the right first questions, decide what's fixed,
go deep where the risk is, watch a late shipment slide the whole critical path and
recover it, then pick your pilot. Then answer real program sense questions out loud
with feedback.
| |
5 | ![]() | A real program sense question reported from Google loops: prepare a program to fix a
city's roads. Marcus answers your clarifying questions, then digs in with follow-ups on
priorities, utilities, paving season, metrics and a mid-program budget cut. Sketch your
plan on the shared notepad. Hiring report after.
| |
6 | Starting a Program from Scratch Document | ||
7 | ![]() | How do you start a program when all you have is a request? In Elena's 3D lab you turn a
vague ask into a measurable goal, place the people on a stakeholder table and win over
the one who could block you, write a one-page charter, settle who decides what, and pick
the moment a launch date becomes a promise. Then answer two classic questions out loud.
| |
8 | ![]() | "How would you initiate a new program from scratch?" Answer it the way a real loop asks
it: Marcus, a senior TPM, lets you lay out your approach, then digs into your metric,
your stakeholders, who decides, when you commit a date and what you do in week one, and
changes the constraints halfway. A shorter ownership question follows. Report after.
| |
9 | Planning and Execution Document | ||
10 | ![]() | Watch a real plan come together and then go wrong in Elena's 3D lab. Break the work down,
estimate it honestly, find the chain of tasks that sets the date, then predict which slip
moves the launch. Lock the date and the team, see what has to give, and win the weeks
back. Then answer two classic execution questions out loud with feedback.
| |
11 | ![]() | You join a program that is a quarter done and has spent most of its money. What do you
do? Marcus, a senior TPM, gives you the facts when you ask for them, then digs into your
numbers, the cause, your options and how you would tell the VP, and tightens the
constraints halfway through. A missed-deadline question follows. Report after.
| |
12 | Managing Program Risk Document | ||
13 | ![]() | Every program bets on something it can't control. On Elena's 3D risk board you find a
program's risks, guess which one to work first, watch mitigations shrink the tall
pillars, set a trigger, and decide what to do the moment a risk fires. Then see how one
buffer keeps a launch date safe. Practise two risk questions out loud with feedback.
| |
14 | ![]() | "Tell me about the biggest risk you took on a program." Marcus, a senior TPM, lets you
tell it, then presses: how likely, how bad, what else you could have done, who signed
off, what each mitigation actually reduced, what you'd have done if the rollback failed,
and what the numbers were. Then a shorter question on how you manage risk day to day.
| |
15 | Process and Agile: Choosing How a Program Runs Document | ||
16 | ![]() | "Is Agile right here?" and "describe a process you created" come up in TPM loops at
Google, Meta and Uber. Watch a plan slip when users see it too late, pick the method
per workstream, see one late API move three teams' sprints, then build a process the
way strong TPMs do: measure the gap, pilot it against a control, win the sceptics.
Answer the real questions and get feedback on the spot.
| |
17 | ![]() | Google asks TPMs how they'd decide if Agile is right for a project, and Uber and Meta
ask for a process you created. Marcus asks both, makes the first one concrete with a
messy real program, and follows up the way real interviewers do, including a vendor
that slips two months. Written report after.
| |
18 | Metrics and Launch: Measure It, Then Ship It Safely Document | ||
19 | ![]() | "How do you develop metrics for a project?" is one of the most asked TPM questions at
Amazon and Google. Build the metrics for a real launch, watch a failed rollback drill
move the go/no-go, halt a rollout when a guardrail breaks at ten percent, and prove
the lift against a holdout. Then answer the real questions and get feedback on the spot.
| |
20 | ![]() | "How do you develop metrics for a project?" and "how do you know it's ready to
launch?" are among the most asked TPM questions at Amazon and Google. Marcus asks both
on a real launch, presses on guardrails, tradeoffs and the rollout, throws in a
capacity surprise two weeks before launch, then asks about a launch you ran. Written
report after.
| |
21 | Technical Depth for TPMs: Architecture, Migrations and Fleet Upgrades Document | ||
22 | ![]() | TPM loops are getting more technical. Walk a real architecture and pick the deep dive,
watch a slow backfill move a migration, size an upgrade of five thousand servers, then
roll it out across four regions and handle the wave that fails. Practise the questions
Google and Amazon ask, with feedback on the spot.
| |
23 | ![]() | Google asks TPMs how they would upgrade five thousand servers, and Amazon asks them to
walk the architecture of a program they ran. Marcus asks both. Ask the right questions,
do the math out loud, design the canary and the waves, and hold up when a wave fails
and security moves the deadline to seventy-two hours. Written report after.
| |
24 | ![]() | How does a system design round actually run, and what gets written on the scorecard?
Learn the four steps and where the minutes go, the five signals interviewers grade,
then scope a real prompt with Nora playing the interviewer: you ask the questions, write
the requirements, pick the deep dive and land the wrap-up.
| |
25 | Running AI and ML Programs Document | ||
26 | ![]() | AI questions now show up in every TPM round. Run an LLM support assistant from data to
adoption with Elena: find the real critical path, hold a launch at the gate, price a
conversation, size the GPUs, shrink the scariest risk and halt a rollout that trips its
eval line. Then answer the questions interviewers ask and get feedback on the spot.
| |
27 | ![]() | Run the launch of an LLM support assistant in a live TPM interview. Marcus wants the
goal in numbers, the critical path, the eval gate, the monthly cost, your top risk and
how you'd roll it out, then throws a vendor curveball. Sketch on the notepad if it
helps. Written report after.
| |
28 | Cross-Functional Partnership and Influence Document | ||
29 | ![]() | Win teams that don't report to you. Place eight partners on Elena's 3D stakeholder map, find
the blocker, predict who to meet first, then watch them walk from blocker to champion as you
meet their goals with your data and a clear ask. Practise two real loop answers, buy-in from a
reluctant team and your first month with a new PM, with feedback and a retry.
| |
30 | ![]() | The cross-functional round of a TPM loop with Marcus, a senior TPM hiring manager. Tell him
about a team that didn't want to help you, and hold up as he digs into their goals, your exact
ask and what you'd do when their VP pulls the engineers. Then: your first month with a new
product manager. Written report after.
| |
31 | Conflict and Hard People Problems Document | ||
32 | ![]() | Two leads stop talking nine weeks before launch. Pick your first move on Elena's 3D
stakeholder map, run the conversation that ends in a decision, watch a half-hearted commitment
push the launch on a 3D plan, and learn to escalate without burning anyone. Then tell your own
conflict story without blame, with feedback and a retry.
| |
33 | ![]() | The question nearly every TPM loop asks, with Marcus, a senior TPM hiring manager: tell me
about a conflict and how you resolved it. He'll ask for the other person's side, who decided
and what you changed in yourself, then throw a curveball. Second: a technical and a people
problem at the same time. Written report after.
| |
34 | Behavioral Stories That Survive Follow-ups Document | ||
35 | ![]() | Behavioral rounds are won on the third and fourth follow-up, not the first answer.
Build a story that holds: STAR plus a learning, a result with a number, the critical
path and the slip, the person you had to win over. Then tell your own program story,
survive Elena's follow-ups on it, and find the gap in your story bank.
| |
36 | ![]() | The behavioral round that decides most TPM loops. Tell Marcus about a program you led
end to end, then hold up while he digs into the plan, the slip, the hardest
stakeholder, the architecture and what you'd do differently. Then a program that went
badly and how you turned it around. Written report after.
| |
37 | Interview Craft Document | ||
38 | ![]() | The whole onsite in one sitting. Marcus plays three interviewers: a senior TPM with a
program to plan, an engineering manager who wants the architecture and a safe
migration, and a hiring manager who keeps asking "and then what did you do?". Clear hat
switches, real follow-ups, a constraint change in each round, and a hiring report that
scores all three.
| |