Choosing the right story
Picking which past example to tell for the question asked: one that matches the skill named, happened at a specific time and place, and shows the quality through what you did. The story is the evidence an interviewer weighs.
What it is
Choosing the right story is the decision you make between hearing a behavioral question and starting your answer: which past example to tell. Behavioral questions ask about a real situation you handled. Amazon says it treats past behavior as the best indicator of future behavior, and that its interviewers judge candidates on examples drawn from their own work history. Under that logic the story is the evidence, and the shape you tell it in (see The STAR method) is how you present the evidence. A well-told story about the wrong thing is weak evidence for the thing that was asked.
| Test | What it means | Fails when |
|---|---|---|
Matches | It is about the skill the question names, not a neighboring one. Handling an unclear requirement is a different skill from working hard under a deadline. | You reach for your most impressive story whatever was asked. |
One moment | It happened at a time and a place, with people who were there, and it ended in something concrete: a figure, or where none exists, the specific feedback you got. | You describe how you usually work. That is a claim about yourself, not an example. |
Shows, doesn't label | What you did makes the quality visible without you naming it. | The story opens with the value's name and asks the listener to take it on trust. |
Yours | You can say what you did in "I" sentences, and what the team did around you. | Your part was watching. Saying "we" throughout hides whether you did anything. |
Fresh | New to this interviewer, and recent enough to reflect your current level. | Each interviewer hears the same accomplishment, or the example is from a much more junior stage. |
You make this choice well in the room by making most of it beforehand. Amazon's advice is to prepare more than one example for each quality it hires for, one or two per principle, so that you can adapt to the wording of the question. It also asks for failures alongside successes, and it describes a candidate who retells one accomplishment for each question as giving a limited view of their experience. A consulting-prep guide suggests the same bank with a mapping step: for each story, write down which qualities it proves, so that when a question arrives in unfamiliar words you can find the fit quickly. One detailed story can serve several themes if you emphasize a different part of it each time.
Build the bank from the job posting rather than from your résumé. Pick out the skills the posting asks for, then find a time you used each one and the figure that shows it worked. Candidates who apply to several similar roles sometimes arrive unclear on which one they are interviewing for. Our advice: settle which role it is before you prepare, because the role decides which stories to have ready. In an automated screen that names a requirement, a strong answer uses the posting's own words for the skill and then gives one time you did that thing, with where and when.
Show the quality instead of naming it. If the question is about ownership, an answer that opens with "I'm someone who takes a lot of ownership" has stated the conclusion and asked the listener to trust it. An answer that opens with the alert that fired in a service your team didn't own, the moment you decided to take it anyway and what you did in the next hour lets the listener reach the conclusion themselves. The same goes for a company's values: skip the company's wording and describe the actions; if they fit, the name is easy for the listener to supply.
Between two stories that both fit, pick the one you can tell in specifics. Amazon's guidance wants most examples to carry quantified results, and where a number doesn't exist it asks for specific anecdotal feedback instead, so a story you remember vaguely is a weaker choice even if the event was bigger. Write the bank down with its numbers and keep it in reach during the interview; candidates who skip that step tend to forget a key example or its figure in the room.
When to use it
Use this step on any question that asks for a past example: "tell me about a time", "give me an example", "describe a situation". It also applies to questions that don't sound like they want a story but are answered better with one:
- A hiring manager asking how you like to work or how you take feedback. The stated preference is one sentence. A strong answer follows it with a time the preference mattered: what the feedback was, who gave it, and what you changed afterward.
- A values question. Pick the story in which your actions show the value, and tell it without using the value's name.
- A screening question that names a requirement from the posting. Choose the time you did that exact requirement, call it by the posting's words, and give where and when it happened.
If the question could be about two different skills, ask which one before you choose. A short clarifying question about what the interviewer wants to know is welcomed in at least one large employer's published advice, and it saves you from telling a good story about the wrong thing. Pausing for a few seconds with "let me think of the best example" is a fair trade for a story that fits.
When not to
- No story fits. Don't bend a near miss to fit the label. Say what you have ("I haven't had that exact situation; the closest is when...") and name the gap yourself. A relabeled story tends to come apart under follow-ups, because the actions don't match the skill.
- The question isn't asking for a story. A hypothetical ("what would you do if...") wants your approach first; see Answering a hypothetical. "Tell me about yourself" wants a short tour, not one example.
- Your best story is the one you just told. With several interviewers, reusing one story gives the panel a narrow view, and a smaller story that is new to this interviewer is usually the better pick. The exception is a direct follow-up on a story you have already told: answer the follow-up.
- The story is your biggest failure. For a failure question you don't need the most serious mistake of your career. Pick one with enough substance to show accountability, the fix and the lesson, without raising doubts about your judgment. See Failure and conflict without blame.
- The story is confidential. Sharing confidential work information is on at least one employer's list of things not to do in an interview. A story you would have to tell in vague terms fails the specificity test anyway, so choose one you can tell in full.
- The story is old. Recent examples are usually easier to tell in detail and reflect your current level. An older story is the right pick when it shows a capability your recent work doesn't.
Compared
| Question | Weaker pick | Stronger pick | When the weaker pick is right |
|---|---|---|---|
"Tell me about a time you worked with an unclear requirement." | Your biggest project, which had a tight deadline. | The smaller ticket where the spec contradicted itself and you had to decide what to build. | When the hard part of the big project really was the ambiguity. Then tell that part and skip the rest. |
"How do you like to get feedback?" | "Direct and early." Stop there. | "Direct and early. Last spring my lead told me my design reviews ran long, so I started sending the doc a day ahead..." | When the clock is nearly out, or a screening form asks for a one-line preference. |
"Tell me about a time you showed ownership." | "I'm very ownership-minded; I treat problems as mine." | The alert in a service your team didn't own, and what you did in the next hour. | When the interviewer asks what the value means to you. Even then, follow the definition with the example. |
Fourth interviewer of the day asks about conflict. | The migration story you told interviewers two and three. | A smaller disagreement this interviewer hasn't heard. | When the interviewer asks a follow-up about the migration story, or when this is the single interview in the process. |
"Describe how you handle competing priorities." | A summary of how you plan your weeks. | The week two launches collided, who you told, and what you dropped. | When the question is a hypothetical about this role's priorities. Then describe your approach and offer the example as support. |
In a picture
How to say it in an interview
The common mistake
Quiz
Related
Sources
- How to use Amazon's Leadership Principles in your interview
- 6 common mistakes candidates make during their Amazon job interview, and tips to avoid them
- I'm a recruiting manager at Amazon: 7 things I'd do differently if I could do my interview again
- 6 things you should never do in an Amazon job interview
- Consulting Behavioral Interview Questions for Experienced Hires (CaseBasix)