How many STAR stories do you need for an Amazon interview?

The short answer: aim for coverage

Eight to twelve stories is often enough to create useful range without making preparation unmanageable. It is a planning guideline, not an Amazon rule. A shorter process may need fewer; a senior or broad role may need more depth, scale and variety.

Your portfolio should let you respond to questions about customers, ownership, judgement, delivery, conflict, failure, learning, simplification and developing others. If several themes depend on the same example, add another story.

A practical 8–12 story portfolio

• Two examples of substantial delivery or measurable impact;
• One customer-driven decision;
• One disagreement, influence or difficult stakeholder situation;
• One failure, missed target or meaningful setback;
• One decision made with ambiguity or incomplete data;
• One process improvement or simplification;
• One example of raising standards;
• One example of developing people or strengthening a team;
• Additional role-specific examples at the right scale.

Test your coverage

For each story, record the primary theme, secondary themes, result, metric, personal contribution and strongest follow-up detail. Ask: Are major themes covered? Do you have successes and setbacks? Does the portfolio show the level expected in the target role?

Add three further checks. First, can you establish Company, Industry and Role quickly enough for a new interviewer? Second, does the Action section explain alternatives and reasoning rather than list tasks? Third, is the result supported by more than a vague claim—whether through numbers, timeline, customer feedback, adoption, quality or another observable outcome?

Finally, review each story for cross-principle risk. A story mapped to Deliver Results should not depend on behaviour that undermines Earn Trust; a story about speed should not casually reveal poor judgement or avoidable quality problems. Replace or reframe stories that create a contradiction you cannot credibly explain.

Review the Leadership Principles question guide against your matrix.

Depth beats volume

Twenty thin stories are less useful than ten examples you can explain under pressure. Know the important numbers, constraints, alternatives and lessons. Expect follow-ups asking what you personally did or why you chose one option over another.

The Amazon STAR method guide shows how to structure this detail clearly.

When can you reuse a story?

Reuse can be reasonable when a story genuinely answers a different question. But heavy repetition narrows the interviewers’ view of you. Treat a story as unavailable after use unless it is unusually strong and the context justifies returning to it.

What counts as a genuinely different story?

Changing the question does not automatically create a new example. If the business problem, your core actions and the result are the same, count it as one story even when it can support several themes. A genuinely different story gives the loop new evidence: another context, decision, stakeholder challenge, type of risk or lesson.

I also look for range across time. A portfolio drawn entirely from one recent project may be easy to remember, but it can hide the breadth of your experience. Older examples can still be useful when they are relevant and you can recall the details reliably. For senior candidates, the bigger question is whether the combined portfolio demonstrates appropriate scale, judgement and influence.

If you have less than a week

Do not rush to write twelve polished answers. Select six to eight high-coverage examples first, identify the most serious gaps, and practise explaining the evidence aloud. Add stories only when the portfolio cannot credibly answer an important theme. This prioritisation is usually more useful than producing a larger set of shallow notes.

Frequently asked questions