Interview prep
How to prepare for an Amazon product manager interview
Amazon's product manager process has a step most PM loops do not: after the phone screen, a recruiter sends a writing exercise that is due two days before the loop, and writing is scored as a competency in its own right2. The loop that follows is five 55-minute interviews, each interviewer assigned different Leadership Principles, with your track record as the main evidence2. So the preparation is two documents in effect: one written recommendation a reader can judge without you, and a bank of past launches deep enough to cover five interviewers.
Last reviewed November 12, 2026
How the interview process works
1.Application
Apply to a team's posting and meet its basic qualifications2. The senior PM postings reviewed, in Bellevue, Austin or Seattle, and Cape Town, ask for about five or more years in product, program or technology roles, roadmap ownership and, in several cases, SQL or data analysis skills456.
2.Phone screen
A 60-minute call with a senior leader on the team, about half behavioral questions on the Leadership Principles and half functional product-management questions; some teams add a second screen2. Budget your stories so the product half is not squeezed.
3.Writing assessment
After a successful screen, a recruiter sends a writing exercise due two days before the loop2. Ask your recruiter what format to expect, and block time for it as soon as the screen is booked.
4.Interview loop
Five interviews of 55 minutes each, with interviewers from Amazon's product management community, each assigned different Leadership Principles2. Five interviewers on different principles means five different projects, not one launch told five ways.
5.Decision
Once the loop is done, Amazon's PM prep page says the decision typically reaches you within 5 business days2.
What this is based on
Amazon publishes a dedicated Product Manager prep page with stages and competencies, and current senior PM postings show what teams ask for. As reviewed on 12 November 2026, that page does not describe the writing exercise's format or say which principles each interviewer covers, so this page does not either. Technical program managers have a separate prep page1.
Practice questions in the style of this role
- Walk me through a feature trade-off you made in a product, program or technology role, including the constraints you faced and the outcome.
- Tell me about a habit you rely on when working with a product or delivery team.
- Suppose the first version of a returns product makes returns easier but also makes them more frequent. What trade-offs does that create for the business and its users?
- Suppose you own the returns-and-refunds experience in an online store. Define one primary metric for how well it works, with its numerator, denominator and time window.
- Describe a time you cut scope or changed a plan early to protect an outcome you owned.
- Walk me through a roadmap you owned end to end, from the problem you chose to the result after launch.
- Walk me through a time you used data to persuade a senior leader to back a direction.
- Walk me through a feature trade-off you made, including the options and what you decided not to build.
- Tell me about a disagreement with a partner team over scope or a feature trade-off that you had to resolve.
- Describe a time you had to bring clarity to an unclear product problem.
A worked example
The question
Suppose you own the returns-and-refunds experience in an online store. Define one primary metric for how well it works, with its numerator, denominator and time window.
Sample answer written for this demo
So I think the main thing a returns experience should do is get people their money back quickly without a lot of friction, so I would pick refund speed as the primary metric. Actually, let me frame it as a rate so it has a numerator and a denominator. The numerator would be the number of returns where the customer got their refund within, say, five days of starting the return. The denominator would be all returns started. And the time window would be weekly, so we can see trends. I like this because it is customer-facing, it captures the whole flow from the return request through the warehouse and the payment, and it is easy to explain to leadership. I would also want to look at a few other things, like the overall return rate, satisfaction surveys after the return, contacts to customer service about refunds, and maybe repeat purchases within 30 days, because a good returns experience should bring people back. In a previous role I worked on a checkout flow and we used a similar rate-based metric for payment success, and it helped us spot problems with one payment provider. So overall I would go with refunds within five days as a share of returns started, measured weekly.
Interview100x's evaluator output, unedited (fill-in gaps shown in brackets)
Ready
You opened with a numerator that was specific about the outcome and the timing: returns where the customer got a refund within five days of starting the return. That gave the metric a clear starting point, and the strongest next step is to build the rest of the definition around it.
- What worked: Your metric definition landed at Ready: you said the numerator is returns where the customer got their refund within, say, five days of starting the return, which is concrete about both the event and the time limit.From the answer:
The numerator would be the number of returns where the customer got their refund within, say, five days of starting the return.
- Next step: State the denominator explicitly, along with the time window over which you would measure, so two people would compute the same number.
- Next step: Explain why this metric reflects the goal of the returns experience.
- Next step: Name the tables or data fields you would pull with SQL to compute it.
- Next step: Restate your refund-within-five-days metric out loud with its denominator, time window, the reason it reflects the returns goal, and the data fields you would query.
- Note: I would measure the share of returns refunded within five days. The numerator is the number of returns where the customer got their refund within five days of starting the return. The denominator is fill in: [what is missing: which returns count, for example all returns started in the period], measured over fill in: [what is missing: time window, for example a weekly cohort of returns started]. I chose this because fill in: [what is missing: why fast refunds reflect the goal of the returns experience]. To compute it, I would pull fill in: [what is missing: the tables or fields, such as return start and refund timestamps] with SQL.From the answer:
The numerator would be the number of returns where the customer got their refund within, say, five days of starting the return.
What the role is evaluated on
- Writing
- The writing exercise is a competency in its own right2. Good looks like: prose a busy reader can act on without you in the room, with the recommendation in the opening paragraph, the evidence behind it, and the risks you see stated plainly rather than buried.
- Leadership Principles through your track record
- Each loop interviewer covers different principles and treats your past work as the main evidence; Amazon says it does not ask brain teasers2. The principles include Customer Obsession, Ownership, Invent and Simplify, Dive Deep, Bias for Action, Earn Trust and Deliver Results, among others3. Good looks like: a distinct project for each principle, with what you personally decided.
- Product management
- Amazon names product management as a core PM competency2. Its postings describe the work as setting vision and roadmap, defining requirements and owning launches and post-launch performance456. Good looks like: a launch story that continues past launch day into what the numbers did and what you changed.
Common ways answers fall short
Writing the assessment like a slide deck
Bullet fragments under headings hide the reasoning. Because the writing exercise is judged as its own competency2, full sentences, an explicit recommendation and named risks make your thinking visible without you there to explain it.
Spending the phone screen on one half
The screen is roughly half Leadership Principles and half product questions2. A ten-minute first story leaves too little time for the product half, and the interviewer ends with only half an assessment.
One flagship launch for every principle
With five interviewers on different principles2, the same launch retold five ways reads as a thin record. Spread your stories across at least three or four projects.
Launch stories that stop at launch day
Amazon's PM postings ask you to own post-launch performance456. A story that ends with 'and we shipped' skips the part where you show what the KPI did and what you did about it.
Only success stories
Amazon asks for examples showing risks taken, failures and what you learned, not only wins2. Across five interviewers, a record where every story ends well reads as curated.
A prep plan for the time you have
One week
A writing sample, a story map and both halves of the screen
- Ask your recruiter whether your team adds a second phone screen and what the writing exercise involves2.
- Map your last five years into a grid of projects against Leadership Principles3, and mark the principles you cannot yet cover with a different project.
- Draft a one-page recommendation on a real decision from your current job, recommendation first, and cut it until a reader needs five minutes.
- Write two stories that include a risk you took or a failure, as Amazon asks2.
- Rehearse a 60-minute screen split roughly evenly between principle stories and product questions2.
- Run one voice practice session on the two risk or failure stories and note where follow-ups found a gap in what you personally did.
Suggested pass: Trial Pass, $12One full voice session tells you whether your stories hold up under follow-up questions before you spend more on practice.
Two weeks
Prepare the writing exercise and five different interviewers
- Week 1: fill the project-by-principle grid so each loop interviewer can hear different work23.
- Week 1: write two practice documents on real product decisions, each with the recommendation, evidence and risks in that order.
- Week 1: refresh SQL basics if your posting asks for SQL or data-querying skills56.
- Week 2: for three launches, write the post-launch story: the KPI, what moved, the root cause you found and what you changed456.
- Week 2: run voice practice sessions where the interviewer follows up twice on each story, and drop stories that lose detail.
- Week 2: keep a day free for the writing assessment once it arrives, since it is due two days before the loop2.
Suggested pass: Sprint Pass, $99Sprint covers unlimited practice for this one job until your interview date, under fair use, which suits repeated story and product rounds over two weeks.
Four weeks
Build a track record you can defend across five interviews
- Week 1: list which responsibilities in your target posting you have done and which you have not456.
- Week 1: for each gap, find the nearest real example and decide how you would describe it honestly.
- Week 2: test every story against two follow-ups: what you personally decided, and how you measured it.
- Week 2: practise one stakeholder story a day where you influenced a senior leader with data46.
- Week 3: write three practice documents and have someone outside product read them cold, then rewrite whatever they misread.
- Week 3: use voice practice for Leadership Principle rounds, one principle per session.
- Week 4: run two five-interview rehearsals around the real writing assessment.
Suggested pass: Sprint Pass, $99A month of preparation for one Amazon PM loop fits Sprint; Search makes sense only if you are interviewing for PM roles at several companies at once.
Questions candidates ask
- What is the Amazon PM writing assessment?
- Amazon says a recruiter sends a writing exercise after a successful phone screen, due two days before the loop, and lists writing as one of the PM competencies2. The prep page, as reviewed on 12 November 2026, does not describe the format, so ask your recruiter.
- What happens in the Amazon PM phone screen?
- A 60-minute call with a senior leader on the team, about half Leadership Principle questions and half functional product-management questions. Some teams add a second screen2.
- How many Leadership Principle stories does an Amazon PM loop need?
- Amazon's PM prep page, as reviewed on 12 November 2026, gives no number. Each of the five loop interviewers is assigned different principles and treats your track record as the evidence2, so prepare enough distinct projects that no interviewer hears a story twice.
- Is the process the same for technical program managers?
- Amazon publishes separate prep pages for Product Manager and TPM roles1, so check which page matches your posting and confirm with your recruiter.
Practice with an interviewer that follows up
A Trial Pass is one full practice session with feedback on your own answers. It counts toward a Sprint Pass if you continue.
Sources
- 1.Interviewing at Amazon · amazon.jobs · undated · accessed 2026-11-12
- 2.Product Manager Interview Prep · amazon.jobs · undated · accessed 2026-11-12
- 3.Leadership Principles · amazon.jobs · undated · accessed 2026-11-12
- 4.Senior Product Manager (Bellevue) · amazon.jobs · 2026-09-22 · accessed 2026-11-12
- 5.Senior Product Manager (Austin/Seattle) · amazon.jobs · 2026-09-22 · accessed 2026-11-12
- 6.Sr. Product Manager (Cape Town) · amazon.jobs · 2026-10-07 · accessed 2026-11-12
Interview100x is not affiliated with, endorsed by, or sponsored by Amazon. Company names are used only to identify the employer. Process details are summarized from Amazon's public pages, linked above; they can change, so check the company's own careers site.
Last reviewed November 12, 2026