InterviewKata
Behavioural interviews · Module 03 of 12 · Level 1: How it works

Building your story bank

You can't prepare an answer for every question, but you can prepare eight to ten stories that answer almost all of them. This module shows how to choose them, map them to what interviewers score, and spot the gaps before an interviewer does.

1. The idea

A chef doesn't cook every dish from scratch at service. They prepare a small set of base sauces in the morning, and each one finishes dozens of different plates. A story bank is your mise en place: eight to ten stories, prepared in advance, each able to answer many different questions.
  1. Collect candidates. List 15–20 moments from the last three years: launches, outages, disagreements, mistakes, things you started, people you helped. Recent and real beats impressive and old.
  2. Keep the best 8–10. Prefer stories where you made decisions, where there was tension or difficulty, and where you know the result.
  3. Map each story to competencies. One good story usually proves three or four: the migration you led shows ownership, ambiguity and influence, depending on which part you emphasise.
  4. Check the gaps. Every competency your target company scores should have at least two stories, so you never tell the same one twice in a loop.
  5. Prepare each one in STAR (Module 02), with its numbers and its three hardest follow-up questions.

The usual competency list, which the rest of this track follows:

CompetencyTypical questionModule
Ownership and results"A time you went beyond your role" · "your biggest impact"04
Conflict"A time you disagreed with a teammate or manager"05
Failure and feedback"A time you failed" · "hard feedback you received"06
Leadership and influence"A time you led without authority" · "mentored someone"07
Ambiguity and trade-offs"A decision with incomplete data" · "competing priorities"08
Customer focus"A time you put the customer first"09
Learning and growth"Something you learned quickly" · "how you've grown"06

2. How it works

A loop with five behavioural questions, and a bank of five prepared stories. Watch each question get matched to a story through the competency it tests, and why the bank needs two stories per competency.

3. Try it yourself

Your story bank grid

Name up to ten stories, then tick the competencies each one could prove. The bottom row counts your coverage: aim for at least two stories in every column. Saved in this browser only.

    4. What interviewers look for

    The story bank is invisible in the interview, but it shows up as range: fresh, specific stories for every question, instead of one story stretched to fit.

    SignalWeakGoodStrong
    RangeThe same project for every answerDifferent stories for most questionsA fitting story for every question, none repeated across the loop
    RecencyStories from many years agoMostly the last few yearsMostly the last two or three years, at the level you're applying for
    FitA story bent to fit the questionA story that mostly fitsThe part of the story that proves this competency, told first
    DepthThin details; follow-ups expose gapsSolid for one or two follow-upsRich under any follow-up: numbers, names of systems, alternatives you considered

    5. A model answer

    "Two different questions, one story." An invented answer, shown part by part. Read it for the shape, then build your own from a true story.

    Question A"Tell me about a time you disagreed with your team." Told from the point where the team wanted to rewrite the billing service and I argued for migrating it piece by piece, the meeting where I brought the data, and how we agreed to trial my approach for one month.

    Question B"Tell me about a time you had to make a decision with incomplete information." The same project, told from the start: nobody knew how many customers used the old invoice format, so I instrumented it for a week before deciding, and planned the migration so each step could be rolled back.

    The bank entryBilling migration (2025). Competencies: conflict, ambiguity, ownership, influence. Numbers: 14 services, 0 billing incidents during the move, 11 weeks. Hard follow-ups: "What if you'd been wrong?", "Who disagreed most, and why?", "What would you do differently?"

    Why it scoresOne well-prepared story gives two different answers, because each question pulls out a different part of it. That's how eight to ten stories cover a whole loop without repeating.

    6. Remember it

    Memory hook: "Ten stories, many angles"A small bank of true stories, each prepared to prove several competencies from different angles.
    How this hook works: what “Ten stories, many angles” means

    What the slogan means, phrase by phrase

    “Ten stories”
    Eight to ten, not forty. Few enough to know deeply, enough to never repeat one in a loop.
    “many angles”
    Each story is a gem with several faces: the conflict in it, the ambiguity, the ownership, the result. The question decides which face you turn to the light.

    Why this picture fits: A cut gemstone shows a different face depending on how you turn it, but it's the same stone. A story is the same: one set of events, turned to show the competency asked about.

    The story → the concept

    The gemYour story
    One stoneOne true set of events
    Each facetOne competency it can prove
    Turning it to the lightChoosing which part to tell first
    A small, well-cut collectionEight to ten stories, deeply prepared

    Watch it on an example

    1. Question: "a time you disagreed." Turn the billing story to its conflict face: the argument and the data.
    2. Question: "a decision without full information." Same story, ambiguity face: the week of instrumentation.
    3. Question: "a time you took ownership." Same story again? Only if no other story fits: check the grid for a second ownership story.

    The trap it saves you from

    Freezing on a question because no prepared story matches its exact wording.

    It still works when…

    The question is phrased in a way you've never heard. Ask yourself which competency it tests, then look in that column of your grid.

    7. Common mistakes

    One hero story for everythingTelling the same big project four times tells the panel you've done one thing. Spread the questions across stories.
    Writing scriptsMemorised paragraphs sound stiff and fall apart under follow-ups. Prepare bullets and numbers, then tell it fresh each time.
    Only success storiesYou'll be asked about failure, conflict and feedback. Prepare real ones; they need the most practice.
    Stories from long agoA story from early in your career shows early-career scope. Prefer recent ones at your current level.
    Forgetting the numbersFind them before the interview: old dashboards, launch emails, performance reviews.

    8. Practice exercise (25 minutes)

    1. Brain dump (8 min). List 15 moments from the last three years. Don't judge them yet.
    2. Choose ten (5 min). Keep the ones with a decision you made, some difficulty and a known result.
    3. Fill the grid (7 min). Enter them in the tool above and tick competencies honestly.
    4. Close a gap (5 min). Pick the emptiest column and find one more story for it, even a small one.

    9. Self-check quiz

    How many stories should a typical story bank hold?

    Enough to cover every competency twice without repeating; few enough to know deeply.

    Why should each competency have at least two stories?

    Several interviewers may ask about the same competency.

    A question uses wording you've never heard. What's the first step?

    Unfamiliar wording usually hides a familiar competency.

    What should you prepare for each story, besides STAR?

    Follow-ups are where stories are tested; numbers make results credible.

    10. Go deeper

    ResourceTimeWhy
    The question bankPracticeRun every story in your bank against questions from its columns.
    The story template5 minOne page per story, with the fields to fill.
    Module 04: Ownership and resultsNextThe first of the five core question types.