Interview Copilot

Amazon behavioral interview: how many stories you need, and how to build them

By Interview Copilot · Checked against amazon.jobs on

Short answer. Prepare 6–8 true stories from your own work and map each one to two or three of Amazon's 16 Leadership Principles, so that every principle is covered by at least one story. You don't need 16 separate stories. Amazon's own prep pages suggest the STAR format (situation, task, action, result) and ask for data where you have it, so each story needs a clear "I", a number or concrete result, and an answer to "what would you do differently?"

What the behavioural part of an Amazon loop checks

Amazon publishes its 16 Leadership Principles, from Customer Obsession and Ownership to Have Backbone; Disagree and Commit and Deliver Results. Its interview-prep pages suggest structuring answers to behavioural questions with the STAR method and backing them up with metrics or data where you can: the interview loop page calls STAR "one way to structure your responses", and the TPM Interview Prep page says "your answers should include metrics or data where applicable". The interview loop page also says "each person will assess different aspects of your skills and experience", which is why you can be asked for a different story by each interviewer.

In practice, most questions take the form "Tell me about a time…" followed by follow-ups: what exactly did you do, what data did you use, what happened next, what would you change.

How many stories: what candidates report

This is the question people ask most. A few real answers:

  • A candidate preparing for an Amazon loop asked "how many stories I should realistically prepare" (r/aws). One reply: "At least two solid stories for each interviewer."
  • A popular r/leetcode post argued that four stories are enough for an engineer's loop. The top reply disagreed: "Amazon asked me 5 stories and the interview prep I went to told me to have 8 stories ready." Another: "I needed 4 stories just for my phone interview" (r/leetcode).
  • In r/AmazonFC, someone moving from dock work to a Process Assistant role was told: "you don't need one story for each of the leadership principles, you need all leadership principles to have a story" (r/AmazonFC).

These are anecdotes, not rules, and loops differ by role and level. They point the same way: enough stories that you never repeat one to two interviewers, and enough coverage that no principle catches you empty-handed. Six to eight usually gets you there.

Build the bank: 6–8 stories, each covering several principles

  1. List candidates. Write down 10–12 moments from the last two or three years where something was at stake: a launch, a mistake, a disagreement, a customer problem, a time you cut scope, a time you were wrong.
  2. Pick 6–8 that are different from each other. You want at least one each of: a result you're proud of, a failure, a disagreement with someone senior, a decision with incomplete data, a time you simplified something, and a time you helped someone else get better.
  3. Map each story to principles. Make a grid: stories down the side, the 16 principles across the top. Tick the two or three each story genuinely shows. A disagreement story often shows Have Backbone; Disagree and Commit, Earn Trust and Dive Deep. A failure story often shows Ownership and Learn and Be Curious.
  4. Fill the gaps. If a principle has no tick (often Frugality, Hire and Develop the Best, or Think Big), find a story for it or adjust one you have.
  5. Write each one as four short lines, not a script: situation (one sentence), task (one sentence), your actions (three bullets, each starting with "I"), result (a number or a concrete change, plus what you learnt).

What makes an Amazon story hold up under follow-up

  • "I", not "we". Interviewers ask what you did. If your story says "we pushed back", expect "what did you do?" Say it before they ask.
  • A result you can defend. A number is best: time saved, errors reduced, tickets closed. If you round or estimate, say so. A made-up metric falls apart at the first "how did you measure that?"
  • Short setup. Most weak answers spend too long on background. Two sentences of context, then your action.
  • A real downside. For failure and disagreement questions, say what it cost and what you changed afterwards. A failure with no cost doesn't sound like a failure.
  • True stories only. In the r/leetcode thread someone joked about making up stories "that fit what they want to hear". Don't: follow-up questions go two or three levels deep, and invented details are where answers break.

When you have no metrics

The r/AmazonFC poster had a common problem: real work, no numbers. Some options that stay honest:

  • Count something. Trucks unloaded per shift before and after a change, how many people you trained, how many days a fix saved.
  • Use a before/after. "We used to re-sort the same pallets every morning; after the change we didn't."
  • Use the scale of the decision. How many people, customers or orders it touched.
  • Use stories from outside your current job if they're stronger. A reply in the same thread: "Use stories not from Amazon if you have to."

Rehearse out loud

A story that reads well on paper can still come out as two minutes of background when you say it. Rehearse each story out loud at least once before the loop:

  1. Answer one question out loud with a story from your bank, as you would in the room.
  2. Pick one thing to fix: usually the setup is too long, the "I" is missing, or the result is vague.
  3. Answer the same question again straight away and compare.
  4. Then answer a question you haven't prepared, using a story from the bank. That's the real test of whether the bank covers the principles.

A friend can play the interviewer. If no one is available, Interview Copilot's AI interview practice (Coach) runs this loop: enter the role and, if you want, the job description, answer likely behavioural questions out loud, get one correction, and retry the same question. The free plan includes 20 practice minutes a month. Scores are a practice signal, not a prediction of Amazon's decision.

For the general five-story method behind behavioural answers at any company, see our guide to behavioral interview questions. For loops with many rounds, see 7 interview strategies for the 2026 job market.

FAQ

How many stories do I need for an Amazon interview?

Prepare 6–8 true stories that between them cover all 16 Leadership Principles, with each story mapped to two or three principles. On Reddit, one candidate reports being asked for 5 stories in their loop, and another needed 4 just for the phone screen.

Do I need one story per Leadership Principle?

No. You need every principle to be covered by at least one story; one strong story can cover several.

Should I use the STAR method?

Yes. Amazon's interview-prep pages suggest STAR (situation, task, action, result) as a way to structure behavioural answers and ask you to include data or metrics where you have them.

Can I use stories from outside work or from a previous job?

Yes, if they are true and show the principle clearly. Recent, work-related stories usually hold up best under follow-up questions.

Sources