What is a story bank, and why prepare one before a set of behavioral interviews?
answer
- Preparation moves recall off the clock
- A small curated set, not everything
- Rows are experiences, columns are themes
- Six to ten, marked strong or usable
- The grid exposes the empty columns
basics
~20 sA story bank is a small, pre-built set of real work experiences — usually six to ten — rehearsed in outline so that any behavioral prompt can be answered by remixing known material instead of searching memory under time pressure.
solid answer
~50 sA story bank is a curated set of six to ten real experiences from your own work, each tellable in two or three minutes, laid out as a story-by-theme matrix: one row per experience, one column per theme an interviewer might probe, each cell marked strong, usable or blank. Building it moves the hard part — remembering what actually happened, deciding what mattered, checking the outcome is something you can defend — out of the room, where you have seconds, and into a quiet afternoon, where you have hours. In the room you are then selecting from known material rather than improvising. The grid also shows you what you do not have: a column with no strong cell is a theme you currently cannot answer well, and that is worth knowing before the loop rather than during it.
go deeper
Know what a story bank is and roughly how big it should be: six to ten real experiences you can tell without notes. Write yours down before your first loop rather than trusting recall on the day.
Be ready to explain the mechanics — rows are experiences, columns are themes, cells are marked strong, usable or blank — and to describe how you built and revised your own grid rather than just naming the idea.
Show that you keep the bank current: new material added while the detail is fresh, rows you can no longer defend retired, and a clear view of which themes your grid cannot cover honestly before you walk into the loop.
Own the tradeoff between a deep bank and a broad one. Rehearsal time is finite, and thin coverage of every theme can leave you with nothing that survives a second and third layer of probing on the theme that actually matters for the role.
## What a story bank is A **story bank** is a prepared, curated set of real experiences from your own working life that you can retell on demand in a behavioral interview. It is not a document you read from and it is not a set of written-out answers; it is an inventory. The usual working size is **six to ten experiences**. Fewer than six and a single loop will exhaust it; more than ten and you cannot keep any of them rehearsed to fluency, so the extra rows are decoration. The organising artefact is the **story-by-theme matrix**: one row per experience, one column per theme an interviewer might probe, and each cell marked *strong*, *usable* or left *blank*. Eight themes is a practical column set for most engineering loops — for example: deadline pressure, disagreement on a team, ambiguity, something that went wrong, mentoring or growing someone, persuading people you do not manage, a technical tradeoff you chose, and an incident under live pressure. A partial matrix for a mobile engineer might look like this: | Experience | Deadline | Disagreement | Ambiguity | Went wrong | Mentoring | Persuading | Tradeoff | Incident | |---|---|---|---|---|---|---|---|---| | Offline sync rework | usable | strong | strong | | | strong | strong | | | Crash spike after a release | strong | | | strong | | | usable | strong | | Onboarding redesign we cut | strong | strong | usable | usable | | usable | strong | | | Battery-drain investigation | | | strong | usable | | | usable | usable | | First release with a new teammate | usable | | | | strong | | | | Read across a row and you see how far one experience stretches. Read *down a column* and you see whether you are covered. ## Why the preparation is worth an afternoon Under interview pressure, recall is the bottleneck, not eloquence. Asked for an example of ambiguity, an unprepared candidate spends the first thirty seconds of thinking time browsing their own career, then commits to whichever experience surfaced first — often the most recent rather than the most relevant. A story bank shifts three expensive decisions off the clock: 1. **Which experience to use.** Already decided, per theme, in the grid. 2. **What actually happened.** Reconstructed calmly, with the sequence, the constraint and your specific part in it checked while you had time. 3. **What the outcome was and how you would defend it.** Verified before, not asserted live and then walked back under a follow-up. What remains in the room is delivery, which is the part you can genuinely do well on the spot. ## Building it: three passes **Pass one — inventory.** Do not start from themes; start from memory and from evidence. Skim your own work log, past retrospective notes, one-on-one notes and release history, and write down every episode where you made a decision, changed someone's mind, broke something, fixed something, or owned something end to end. Aim to over-collect, then trim to the rows worth rehearsing. **Pass two — mark the grid.** For each experience, go theme by theme and mark honestly. *Strong* means the experience genuinely contains that theme and you can talk about it for several minutes with real detail. *Usable* means it touches the theme but is not the best material you have. *Blank* means it does not fit, and pretending otherwise will collapse under probing. **Pass three — fix the columns.** A theme with no strong cell is a hole. Fill it by mining more of your history, not by inventing. If it is genuinely empty — you have never run an incident, for example — plan an honest answer for that case rather than manufacturing one. ## Rehearsal, and the mistake to avoid Each row is rehearsed from a short cue outline of about five to seven beats, said aloud, ideally with a mock-interview partner who interrupts. The failure that ruins otherwise good preparation is **writing all six stories out word for word and memorising them**. Scripted delivery is audible: the phrasing is too smooth, the answer does not bend toward the prompt actually asked, and the first interruption derails it. An outline fixes the beats and leaves the words free. ## What a story bank is not It is not a script. It is not fiction — every row must be something you did, told with your own contribution described accurately. It is not a static document either: after a significant project, add the row while the detail is fresh, and retire rows you no longer remember well enough to defend.
- How is a story bank different from simply rereading your resume before the interview?A resume lists projects and outcomes; a story bank stores the narrative underneath them — the constraint, the decision, your specific part, the result. Rereading a resume reminds you what you worked on but leaves the retelling to be improvised. The bank also indexes that material by theme, which a resume never does, so you know in advance which experience you will reach for.
- How many experiences do you actually need for a full day of interviews?Six to ten rows is the working range. A day of several conversations can easily consume four or five distinct experiences, and interviewers who compare notes afterwards notice repetition, so a bank of two or three runs dry. Beyond ten, rehearsal time thins out and the marginal rows are ones you tell badly.
- Should the matrix be written down, or is keeping it in your head enough?Write it down. The value is in reading columns — spotting that a theme has no strong cell — and that comparison is hard to do mentally. A one-page grid plus a short cue outline per row is enough; anything longer starts turning into a script you will be tempted to memorise.
saying these in an interview costs you the question
- Preparing one strong experience and stretching it across every prompt
- Writing all six stories out word for word and reciting them
- Inventing or borrowing an experience to fill an empty column
- Collecting experiences but never saying one aloud before the loop
- Treating the grid as a document to read from during the conversation