How to build an interview story bank: one story, several answers.

Updated · Sources at the end

An interview story bank is a small set of true experiences from your work that you can adapt to any behavioural question. You prepare the material once, then shape it to whatever they ask, which holds up far better than a memorised answer when the wording changes. This guide covers how many stories you need, which ones, a worked example, and a template to copy.

Free · on this page · no account

Write your stories in the four lines, with checks as you type.

Write my first story ↓Or predict the questions for my job →

Saved in this browser. Nothing is sent anywhere.

01

How many stories do you need?

6–7

stories for a single interview or an early round

8–12

for a full onsite loop with several behavioural rounds

~2 min

for each story told out loud, before follow-ups

Fewer than most people think, because one good story answers several questions. Published advice lands on a small number:

  • 5–8a developer's guide to a career story bank
  • 6an r/interviews thread: “build a 6-story bank instead” of memorising scripts
  • 7–10a university career centre's story bank worksheet
  • 8–12a guide to leadership interviews for a full onsite week

The difference is how many rounds you face. One interview draws on your six or seven strongest stories. A full onsite loop needs eight to twelve, because several interviewers each ask behavioural questions, they compare notes afterwards, and a story told twice leaves a theme with no evidence. Past twelve, each extra story costs more rehearsal than it earns.

Which questions your bank has to answer depends on the job. Paste the posting and Calibrd predicts them, round by round, for that role and level.

Predict my questions →
02

Build it in an hour: five steps

  1. Go through your CV, role by role. For each job, write down every project, problem, disagreement and mistake you remember. Aim for twenty rough candidates; most will not make the cut.
  2. Pick six to twelve. Keep the ones where you made a decision and can describe a result. Drop the ones where you mostly watched.
  3. Write each one in four lines. Situation, what you did, what changed, what you learned. See a finished one, then write yours on this page.
  4. Tick the themes on a grid. Every story should cover two or three themes, and every theme should have at least two stories. How the grid works.
  5. Say each one out loud. Time it at about two minutes, then answer the follow-ups you would ask yourself. How to practise them.
03

Which stories to put in it, and the questions they answer

Pick experiences that show different things. These five themes come up again and again in behavioural rounds, and they are the ones Calibrd's Story bank tags. Under each are questions that are commonly asked for it, so you can check which story you would use.

Theme 01

Ownership

Something you drove to a result without being told to.

  • “Tell me about a time you took on something outside your role.”
  • “Describe a project you drove from start to finish.”
  • “What's your greatest achievement?”
How to answer “What's your greatest achievement?” →

Theme 02

Collaboration

A disagreement or a dependency you worked through with other people.

  • “Tell me about a time you disagreed with a colleague or your manager.”
  • “Describe working with someone who was hard to work with.”
  • “Tell me about a time you depended on another team to deliver.”
How to answer “Tell me about a conflict” →

Theme 03

Leadership

People you moved, whether or not they reported to you.

  • “Tell me about a time you influenced people who didn't report to you.”
  • “Describe getting a team behind a decision they didn't like.”
  • “Tell me about someone you helped grow.”

Theme 04

Technical depth

The hardest problem in your field you have actually solved.

  • “What's the hardest problem you've worked on?”
  • “Tell me about a decision you would make differently now.”
  • “Walk me through a complex project, end to end.”

Theme 05

Failure

Something that went wrong, what you did about it, and what you changed after.

  • “Tell me about a time you failed.”
  • “Describe a mistake you made and how you handled it.”
  • “Tell me about a deadline you missed.”
How to answer “Tell me about a time you failed” →
04

What a finished story looks like

Four short lines per story: the situation in one sentence, what you did, what changed because of it (a number if you have one), and what you learned. That is the STAR method with a learning added. Keep the situation short: interviewers spend their follow-ups on what you did and why, so that is where the detail belongs.

The release that kept slipping

OwnershipCollaborationFailure
Situation
Our quarterly release had slipped twice, and the launch date the sales team had promised customers was four weeks away.
What I did
I listed every open item with its owner, cut three features with the product manager after showing her what each one cost in days, and set up a fifteen-minute daily check with the two teams we depended on.
What changed
We shipped on the promised date. The three features followed six weeks later, and the daily check became how the team ran every release after.
What I learned
I had waited too long to raise the slip. Now I flag a date at risk as soon as the plan stops adding up, with the options to fix it.

An illustrative example. Your bank uses your own experiences, with your own numbers.

One story, three themes: it answers “Tell me about a project you drove,” “Tell me about working with another team” and, through the last line, a question about a mistake. When two stories could answer the same question, use the one with the larger scope. Hello Interview makes the same point in its behavioural guide: map the question to the area it is testing, then “choose the one that has the highest scope.”

05

Write your stories

Use the same four lines here. The checks flag the mistakes that sink a good story as you type, save each story to a bank in this browser, and show which themes still need a second story. Nothing is sent anywhere.

Story builder · saved in this browser only

Themes it shows up to three

Fill in the situation, what you did and what changed to save it.

Prefer your own document? Copy the template

The same four lines, one block per story, for a document or a spreadsheet. The “questions it answers” and “follow-ups” lines are what make it a bank you can use under pressure.

Template · one block per story

STORY BANK

Story: [a short name you will remember it by]
Themes: [two or three of Ownership, Collaboration, Leadership, Technical depth, Failure]
Situation: [one sentence: where you were and what was at stake]
What I did: [the decisions and actions that were yours, said with "I"]
What changed: [the result, with a number if you have one]
What I learned: [what you do differently since]
Questions it answers:
- [question]
- [question]
Follow-ups to expect: [why that approach? what would you change?]

(Repeat for six to twelve stories, then tick each story's themes on a grid.)
06

Map stories to questions on a grid

The grid is the part most people skip, and it is what turns a list of anecdotes into a bank. Put your stories down the side and the themes across the top, then tick each theme a story can answer. Two rules make it work: every story should tick two or three themes, and every theme should have at least two ticks, so you have a second choice when the first story doesn't fit the question.

Example grid. Replace the rows with your own stories.
Your storyOwnershipCollaborationLeadershipTechnical depthFailure
The project you are proudest of✓✓✓
A disagreement you worked through✓✓
Something that went wrong on your watch✓✓
A problem nobody else picked up✓✓
Leading people you didn't manage✓✓
A decision made with too little data✓✓

Six stories, every theme covered at least twice. Before an interview, add a column for each question you expect from that company and fill in which story you would use. A question with no tick is the gap to close before you walk in.

07

Practise them out loud

A story bank on paper is half the work. The other half is being able to tell each story in a couple of minutes, out loud, and answer follow-ups on it without losing the thread. Say each one aloud a few times in different wordings, so you know the story rather than one version of it. If an answer wanders when you say it, you can talk it through and get it back in STAR order. Every story has to be true: follow-ups go several levels into the same story, and a borrowed or embellished detail doesn't survive the third question.

Then test the bank the way the interview will. A mock interview asks the round's questions in an order you don't control, follows up on each story, and grades the round. You only pick the role you're preparing for; a job posting is optional.

Run a mock interview →
08

Keep and rehearse them in Calibrd

The builder above keeps your stories in this browser. Calibrd's Story bank keeps them on your account and builds on them from your practice. Answer a predicted question out loud or in writing, get it graded, and keep it as a story: its situation, what you did, the impact and what you learned, tagged with one of the five themes above. Answers about the same experience are grouped into one story, a check flags any line that didn't come from your own answers, and each story lists the questions it answers, linked to the job you answered them for.

For a job you are preparing, the Story bank also lists the predicted questions that none of your stories answers yet: the empty columns in your grid, worked out from that job's rounds.

Build your stories with a free account. Anything you wrote in the builder above comes with you, and the Story bank shows which of a job's questions they don't cover yet.

Build my Story bank →
09

Mistakes that sink a good story

  • Saying “we” all the way throughThe interviewer is assessing you. Say what the team did in one line, then “I” for every decision that was yours.
  • No result at the endA story that stops at the action leaves the interviewer to guess. Close on what changed, with a number if you have one, or what you would do next time.
  • A long situationOne or two sentences of background is enough. If the setup takes a minute, the part they score gets squeezed.
  • The same story twice in one loopInterviewers compare notes. Plan which story goes to which round, and keep a second story ready for every theme.
10

Early in your career, or interviewing as a manager

Graduate or junior

Internships, university projects, part-time jobs and volunteering all count. Interviewers expect it. Six stories is enough, as long as each shows a decision you made and a result you can describe.

Senior or manager

Weight the bank towards leadership: hiring, growing someone, a hard performance conversation, a team you turned around. Expect a separate people-management round that draws on three or four of these alone.

11

Amazon: one bank, sixteen principles

Amazon is the sharpest case of this, because every interview in its loop is also a Leadership Principles interview. Its own advice to candidates, on Amazon's careers blog, is to read the principles and “identify one or two work anecdotes that are relevant to each one.” With sixteen principles that sounds like thirty stories, but one story usually shows two or three principles, and prep guides suggest eight to twelve stories, mapped on the same kind of grid with the principles as the columns. Our Amazon interview guide covers the loop, the Bar Raiser and how deep the follow-ups go.

·

FAQ & sources

What is an interview story bank?

A small set of true experiences from your work, each written down in a few lines, that you adapt to whatever behavioural question you are asked. Instead of preparing an answer per question, you prepare six to twelve stories and map each one to the questions it can answer.

How many STAR stories should I prepare?

Start with six or seven stories that cover the questions asked most often: a result you drove, a conflict, a failure, leading without authority, and your strongest technical or functional work. For a full onsite loop of several behavioural rounds, aim for eight to twelve. Fewer than eight and a question can catch you with nothing that fits; past twelve, each extra story costs more rehearsal than it earns.

Can one story answer several interview questions?

Yes, and a good bank depends on it. A story about fixing a production outage overnight can answer questions about ownership, working under a deadline and dealing with an incident. Aim for each story to cover two or three themes, and for each theme to have two stories, so you have a second choice when the first one doesn't fit the question.

What should each story in the bank include?

The situation in one sentence, what you personally did, what changed because of it, with a number where you have one, and what you learned. That is the STAR method with a learning added. Keep the situation short: interviewers spend their follow-up questions on what you did and why.

How long should each story be?

About two minutes when you say it out loud. That leaves the interviewer time for follow-up questions, which is where most of the assessment happens. If a story runs past three minutes, the situation is usually too long.

What if I don't have much work experience?

Use internships, university projects, part-time jobs, volunteering and anything you organised. Interviewers for entry-level roles expect it. What matters is that the story shows a decision you made and a result you can describe.

Can I reuse the same story with different interviewers?

Yes, across different rounds or companies. Within one loop, try not to tell the same story twice, because interviewers compare notes and a repeated story leaves one theme with no evidence. That is why a full loop needs eight to twelve stories.

How many stories do I need for an Amazon interview?

Amazon's own interview advice is to identify one or two work anecdotes for each Leadership Principle. Because one story can show two or three principles, that does not mean thirty separate stories: prep guides suggest eight to twelve, mapped on a grid. Expect follow-up questions that go several levels into the same story, so every story has to hold up under detail.

Should I memorise my interview answers?

No. Prepare the stories and practise saying them out loud in different wordings. A memorised answer breaks when the question is phrased differently; a story you know well bends to fit it.

Your stories, built from your answers

See which questions your stories don't answer yet

Paste a real job and Calibrd predicts the questions each round asks. Answer them out loud, get each answer graded, and keep them as a story bank that shows which questions are still uncovered.

Not interviewing yet? Every morning Calibrd reads the careers sites of 500+ companies and checks each new job against your experience the way a hiring manager would. Get job alerts →

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

How to Build an Interview Story Bank (+ Template) · Calibrd