Program Manager
Amazon · L5
Recommended next: your first attempt
Do the Program and Leadership screen round.
A complete first attempt shows where you stand before any narrow practice starts.
The loop
Pick a round to see what it asks of you and where you stand on it.
Program and Leadership screen
Learn whether the candidate has L5 program judgment and specific Leadership Principle evidence before the full loop.
Behavioral · 60 minSet up this round
Not tried yetNo attempt yet.
What strong sounds like
- Show direct responsibility from ambiguous need through corrective action and delivery.
- Clarify workstreams, owners, dependencies, milestones, and operating cadence.
- Use customer, quality, cost, or cycle-time evidence and explain attribution.
- Name a planning assumption that failed and the mechanism changed afterward.
Expect to be pushed on
Change one important constraint and ask what survives.
Probe the weakest assumption and the evidence needed.
Ask for the rejected alternative and decision threshold.
Shapes of problem you may get
- Two or three program-delivery stories with functional follow-ups on risks, metrics, and mechanisms
How to prepare
- 01
Select quantified delivery stories
Choose three L5 examples covering ambiguity, corrective action, and cross-functional delivery. Record your decision, personal ownership, measures, failed assumption, mechanism change, and unresolved risk.
Amazon officially describes a 60-minute screen with Leadership Principles and functional program questions. Recent L5 reports also emphasize quantified examples that withstand follow-ups.
Company researchAmazon Program Manager Interview PrepAmazon L5 Program Manager interview discussion
A first attempt takes the full 60 minutes.
What this loop tests
Amazon publishes the Program Manager loop: a 60-minute screen split between program-management and Leadership Principle questions, a writing assessment due two days before the loop, and five 55-minute interviews. Prepare quantified examples of end-to-end delivery, mechanisms, risk control, stakeholder alignment, and customer impact. Functional cases should show how you turn ambiguous work into owners, dependencies, metrics, and corrective action.
They reward
- Customer outcomes over activity metrics
- Ownership through durable mechanisms
- Dive Deep before correcting course
- Risk control with decisive action
- Earn Trust across global partners
- Clear writing for decisions
What to avoid
- Do not substitute a memorized framework for the supplied facts.
- Do not hide personal decisions behind vague team language.
- Do not claim certainty beyond the evidence available.
How sure we are
Worth redoing if you hear something from the recruiter that contradicts this.
Attempts
Every session saved against this target, newest first. Standings live on the round cards.
Program and Leadership screen, Writing assessment, Program mechanisms and delivery, Dive Deep and course correction, Stakeholder alignment, Risk and adaptability, and High standards and judgment have no attempts yet.