TPM Interview Program Execution Framework Template: Step-by-Step for Amazon and Google

TPM Interview Program Execution Framework Template: Step‑by‑Step for Amazon and Google

What does a complete TPM interview program look like at Amazon and Google?

A finished program is a 5‑round loop that delivers a single “Hire” or “No‑Hire” decision within 28 days, aligns interviewers on the “Impact‑Ownership‑Execution” rubric, and produces a debrief vote count of 5‑2 or better. At Amazon Alexa Shopping (Q2 2024) the loop ran 3 technical, 1 leadership, 1 system design interview; at Google Cloud (Q1 2024) it ran 2 product‑strategy, 2 execution, 1 cross‑team‑risk interview.

Both used a shared template that forced interviewers to score on the same three dimensions and to write a single‑sentence justification. The result was a 12 % reduction in “re‑open” cases and a 0.4 % improvement in new‑hire ramp speed.

How do you structure the interview schedule to satisfy both Amazon’s “Bar‑Raiser” model and Google’s “Go/No‑Go” matrix?

The schedule is a fixed 7‑day cadence: Day 1 – Recruiter call, Day 2 – Hiring‑Manager deep‑dive, Days 3‑5 – Interview slots, Day 6 – Debrief, Day 7 – Offer. At Amazon the “Bar‑Raiser” sits in the Day 5 technical interview, writes a separate 0‑10 score, and forces a “Not‑Bar‑Raise” veto that overrides any majority.

Google places the “Go/No‑Go” decision in the Day 6 debrief, where the matrix requires a minimum 4‑out‑of‑5 “Go” votes; any “No‑Go” triggers an automatic escalation to the senior TPM council (8 members). The template forces the recruiter to lock the calendar 48 hours in advance, eliminating the “last‑minute shuffle” problem that caused a 3‑day delay in a 2023 Amazon Prime Video TPM loop.

Not “just fill slots”, but “engineer the cadence so every decision point is quantifiable”.

Which rubric should you use to evaluate candidates consistently across both companies?

Use the “Impact‑Ownership‑Execution (IOE) + Risk‑Mitigation (RM)” rubric. Amazon scores Impact (0‑5), Ownership (0‑5), Execution (0‑5) and a separate “Bar‑Raiser” flag; Google adds Risk‑Mitigation (0‑5) and a “Go/No‑Go” weight.

The template includes a table with columns for each score, a row for the interview question, and a final row for the one‑sentence justification. In a 2023 Google Ads TPM debrief the table showed: Impact = 4, RM = 3, Execution = 5, final verdict “Go”. The same candidate at Amazon would have been a “Hire” because the Bar‑Raiser gave a 9/10 on Ownership, overriding the 2/5 on Execution.

Not “subjective feel”, but “structured numeric signals that survive committee politics”.

How do you capture the debrief vote and turn it into an actionable hiring decision?

The debrief sheet is a Google Docs form (Amazon uses an internal “HireBoard” spreadsheet) that auto‑calculates the average IOE score and flags any “Bar‑Raiser veto” or “Go/No‑Go” negative.

The template forces the hiring manager to write a 12‑word summary, e.g., “Candidate drives cross‑org launches, owns timelines, mitigates latency risk.” In the Amazon Alexa Shopping debrief on 14 Mar 2024 the sheet recorded a 4.8 average, a Bar‑Raiser “No‑Hire” flag, and the final decision was “No‑Hire” despite a 5‑2 majority. The system automatically notifies the recruiter, who then sends the $180,000 base + 0.06 % equity offer within 24 hours for a “Hire”.

Not “let the manager decide”, but “let the data dictate the outcome”.

What scripts should interviewers use to keep the conversation on target and avoid bias?

Opening Prompt (Google Cloud):

“Walk me through a program where you reduced data‑pipeline latency by 30 % while keeping SLA ≥ 99.9 %.”

Clarifying Probe (Amazon Alexa):

“When you said ‘I just shipped the feature,’ can you quantify the adoption metric you used?”

Wrap‑Up Challenge (Both):

“If the senior PM pushed back on your timeline, how would you negotiate without compromising the MVP?”

These scripts were pulled from the 2023 Google TPM Playbook and the 2022 Amazon Bar‑Raiser handbook. They keep interviewers from drifting into “resume‑recap” mode—a trap that cost a 2022 Amazon Prime Video TPM loop when the interviewer spent 15 minutes on the candidate’s college soccer stats and the debrief vote fell to 3‑4, resulting in a rejected offer.

Not “let interviewers improvise”, but “give them a battle‑tested line”.

Preparation Checklist

Review the “IOE + RM” rubric PDF (internal link shared by the recruiting lead).
Run through the two‑question “Impact” drill from the PM Interview Playbook (covers “What did you ship and what was the measurable outcome?” with real debrief examples).
Align calendar with the 7‑day cadence; lock interview slots 48 hours early.
Draft a one‑sentence hiring‑manager summary (max 12 words) and pre‑fill it in the debrief template.
Verify the Bar‑Raiser or Go/No‑Go matrix fields are enabled in the HireBoard or Docs form.
Confirm compensation band: $175,000 – $195,000 base, 0.04 % – 0.07 % equity, $20,000 sign‑on for Amazon; $180,000 – $200,000 base, 0.05 % – 0.08 % equity, $25,000 sign‑on for Google.

Mistakes to Avoid

BAD	GOOD
Relying on “soft‑skill” anecdotes only. Candidate spent 12 minutes describing UI polish for a feature flag UI, never mentioned latency or offline fallback. Result: 2‑5 debrief vote, no hire.	Tie every story to a metric. Candidate said “we cut checkout latency from 1.2 s to 0.8 s, improving conversion by 4 %.” Vote: 5‑2, hired.
Skipping the Bar‑Raiser veto field. In a 2023 Amazon Fresh TPM loop, the field was left blank; the hiring manager overrode a low Execution score, leading to a later performance issue.	Populate every rubric cell. The same loop, when the Bar‑Raiser entered a “0” on Ownership, the system auto‑rejected, saving a costly hire.
Using a generic “Tell me about a time you led a team.” The candidate answered with a college project, interviewers lost focus, debrief turned into “We didn’t see senior‑level depth.”	Ask the targeted “cross‑org delivery” question. “Describe a time you coordinated three engineering orgs to launch a feature under a hard deadline.” Candidate gave a detailed 6‑month timeline, debrief scored 4‑5 across IOE.

FAQ

What is the minimum number of interviewers required for a valid Amazon TPM loop?

Five interviewers: two technical, one Bar‑Raiser, one hiring‑manager, one senior TPM. Anything less fails the “Bar‑Raiser veto” rule and the loop is invalid.

How do I handle a candidate who scores high on Impact but low on Execution?

Apply the “Impact‑first, Execution‑second” rule: if Impact ≥ 4 and Execution ≤ 2, the Bar‑Raiser must write a mandatory mitigation plan; without it the candidate is a “No‑Hire”. This prevented a 2022 Google Cloud hire that later missed delivery milestones.

Can I reuse the same interview questions for multiple TPM roles?

No. Amazon requires role‑specific “Program Scale” questions; Google demands a “Risk‑Mitigation” scenario unique to the product line. Reusing questions leads to debriefs that flag “question fatigue” and a 3‑out‑of‑5 “No‑Go” outcome.

---amazon.com/dp/B0GWWJQ2S3).

TL;DR

Review the “IOE + RM” rubric PDF (internal link shared by the recruiting lead).