Building a Story Bank

You can't prepare an answer for every behavioral question. There are hundreds of wordings, and interviewers make up new ones. But most of them ask about the same dozen or so things: leading, disagreeing, failing, deciding without enough information, winning people over, choosing what to drop. A story bank is 8 to 12 real stories that between them cover those things, each prepared well enough to tell in 2 to 3 minutes and to defend under questioning. With one, a new question stops being a test of memory and becomes a choice of which story fits.

Start with your resume. Every strong bullet is the short version of a story, and the story is usually more interesting than the bullet. "Moved billing to a new payments provider" might hide a deadline you renegotiated, a bug you caught the night before launch, and an argument about whether to move at all. For each bullet, ask:

• What went wrong? Setbacks, near-misses and surprises make the best stories, and they answer the questions people dread most.
• What did you decide? Every real decision had options you turned down. Those become your answer to "why that approach?"
• Who disagreed? Pushback from a manager, a peer or another team is your material for conflict and influence questions.
• What changed? The result, measured if you can. If nothing changed, you may have found a failure story, which is just as useful.

Aim for coverage, not a pile of similar wins. Between them, your stories should show leadership, conflict, failure, ambiguity, influence and prioritization, and ideally a time you helped someone else grow. Spread them across jobs so the interviewer learns about you and not one project. Lean recent, since newer stories are closer to the level you're applying for and you'll remember the details. Look past the resume too: the outage you handled at 2 a.m. rarely makes a bullet, and often makes the best answer. Most good stories show more than one thing, so map each one to every kind of question it could answer.

                      Lead  Confl Fail  Ambig Infl  Prio
Payments migration     x     x                       x
Search outage                      x     x
Deadline pushback            x                 x     x
Onboarding revamp      x                       x
Vague product ask                        x     x     x

Write each story down in STAR form: a sentence or two of situation and task, your actions in order, the result with its numbers, and what you learned. Under it, note what follow-up questions will reach for: the options you turned down, who else was involved, and how you measured the result. Then tell each story out loud, more than once. Writing fixes the facts. Telling is what gets a story under three minutes and makes it sound like you rather than a script.

Keep the bank current. Add a story while it's fresh and you still know the numbers, rather than rebuilding it from a resume bullet a year later. After each interview, note which stories you used and which questions you had nothing good for. If you'd like somewhere to keep it all, your story bank in Resland stores each story in STAR form, tagged with what it shows. Its coverage grid shows which kinds of question you have no story for yet, and live checks flag a story that says "we" more than "I", a result without a number, or a telling that runs too long.