Stage 4 · Interviews · 5 min read

Story Bank Guide: Eight Stories That Cover Thirty Questions

Interviews ask the same questions in different clothes. Build eight real stories to an 8/10 and you have an answer for almost all of them.

Contents · 5 sections Close contents

Candidates who prepare by downloading "The 100 Most Common Interview Questions" arrive with 100 half-answers. Candidates who walk out with offers arrive with about eight stories they can tell from any angle, each one said out loud enough times that the numbers come without reaching.

The reason this works is that interview questions are not 100 different things. "Tell me about a conflict", "Tell me about a time you disagreed with your manager" and "How do you handle pushback?" are one story asked three ways. The job is to find your eight, build each to an 8/10 on the Bashmo rubric, and keep a map of which story answers what.

1. Mine the Last Two or Three Years

Go through your last two roles with these prompts and write down every candidate, one line each. Do not judge them yet; aim for twenty lines.

Prompt	What you are looking for
A disagreement	With a peer, a manager, a client or a family member of a patient; one where something was decided
A deadline or a surge	The week the plan broke; what you cut, who you told, what still shipped
A failure that was yours	A call you got wrong, with a consequence and a change you made afterwards
A time you persuaded someone	A stakeholder, a skeptical senior, a classroom; evidence over position
Something you learned fast	A tool, a protocol, a codebase, a curriculum, under a clock
A thing you built or fixed	A process, a checklist, a system, a rota; with a before and an after
A customer, patient, student or user moment	One person, one hard conversation, one outcome
A time you said no, or cut scope	Where you chose what not to do, and why
A time you led without the title	People who did not report to you, doing what you asked

Then pick eight: the ones with a real moment, a number you can defend, and a part that was clearly yours. Two from each of your last two roles is a good shape. A story from five years ago is fine if it is the best example; two from five years ago raises the question of what you have done since.

2. The Story Matrix

Lay the eight stories against the questions they can answer. This is the whole method, on one page:

Story (one line each)	Conflict	Pressure	Failure	Persuasion	Fast learning	Deep dive
The weekend rota I rebuilt with Dana	Lead			Yes
The ERP migration that lost two seats		Lead		Yes		Yes
The macro set that cut response time to 45 min		Yes				Lead
The go-live I called wrong in week three			Lead
Convincing the department to keep the exit tickets	Yes			Lead
Learning the billing system in nine days					Lead
The dead-letter queue rollout		Yes		Yes		Lead
The night I had six patients and one aide		Lead

A Lead is the story you reach for first when that question comes; a Yes is the backup if the lead has already been used in that interview. Every column should have at least one lead and one backup. If a column is empty, go back to the mining list; that is the question you are currently unprepared for.

Try a question

Try it on this guide’s questionFree · no account · 5 questions

Five questions free here, no account. Sign in with your email to keep your best answers and get your full plan.

Your field:

“Describe a time you went above and beyond what was asked of you. What drove you, and what came of it?”

Say it or type it; about a minute and a half is enough.

3. Build Each Story to an 8

A story is ready when it holds the four parts in about a minute and a half (100–250 words), said out loud, and survives one follow-up. The shape:

The situation, 15 seconds. Team size, the constraint, the stakes. Stop before the history of the company.
The moment and your action, 40 seconds. Two or three specific moves you made. Name a person by first name or role. Name the trade-off.
The outcome and the habit, 20 seconds. The number that changed, and the one thing you kept doing afterwards.

Then the loop that turns a 5 into an 8:

Say it, do not think it. A story thought through silently feels like a 9. The first time it is said out loud it usually scores around 4.5: the order wanders, the number is missing, it is all "we". Say it into Bashmo and read the 0–10.
Apply the one fix, then say it again. Each score comes with the single change that lifts it most: name the colleague, state the before-and-after, replace "we decided" with what you did. One fix per take. Most stories reach an 8 on the third or fourth take.
Keep the 8. At 8, Bashmo keeps the answer as your best for that question. That is the version you say in the room, and the version you adapt when the question comes in different clothes.

The Same Story, Three Questions

The rota story above, told as a lead for conflict, opens on the disagreement with Dana. For persuasion, the same story opens on the twenty-minute meeting with the schedule and the sick log side by side. For a deep dive into "a process you improved", it opens on the five Saturday sick calls a month. Same facts, same number at the end, different first sentence. Practice each opening once.

4. Which Stories Matter Most in Your Field

Every field asks the five core questions. Each also leans on one or two story types harder than the others:

Field	Build these first	Why
Nurse	Pressure (a short-staffed shift), a near miss, a hard family conversation	Safety culture and triage judgment decide the hire
Teacher	A lesson that failed, assessment data that changed your teaching, a parent conversation	Adaptability and data use are the whole interview
Sales	A deal nearly lost, a quarter behind, an account you grew	Every question is a version of "show me the number"
Customer support	A repeating problem you fixed at the root, a customer you had to say no to	Judgment beyond the macro and product sense
Project manager	Fewer resources than planned, a stakeholder who kept changing scope, a risk you caught early	Trade-offs and alignment under a moving target
Engineer	A migration or rollout, an incident and what it changed, toil you removed	Reliability thinking and the "what broke?" follow-up

5. Keep the Bank Alive

The bank is not finished when the first interview is booked. It compounds if you feed it:

After every interview, write down every question asked, within two hours. Add the ones your matrix did not cover. Those are next week's practice.
Retire the weakest story when a better one shows up. Eight is the number because it fits in a head under pressure. Twelve does not.
Re-score the leads before each loop. A story that held an 8 in March drifts by June. One take on Bashmo two days before an interview tells you whether the numbers still come without reaching.
Watch the one number per interview. When you add a position with its posting and your resume, Bashmo writes the role's own questions around your core ones and shows one % ready for that interview. The bank is what moves it.