The highest-return two hours of your prep
One story answers four or five different questions. Ten well-chosen ones mean you never face a behavioural question without material. Everything you type saves in this browser as you go.
Not full STAR. In a real conversation the situation gets one sentence and the action gets two, because interviewers interrupt long set-ups and the interruption always lands on the part you needed. Five fields, and the last two matter most:
Two rules that save you in the room
Don't reuse a story twice in one interview. If you've used the adoption failure for "tell me about a failure", you need a different one for "tell me about a time you were wrong." Two stories with the same shape reads as having only one.
Ninety seconds. If a story needs three minutes of set-up to make sense, it's the wrong story for an interview, however good it was in real life.
Decide what you want them saying about you afterwards. Write them here, put them on the card you take in, and check them off mentally as they land. People remember three things from an hour — if you don't choose them, they choose themselves badly.
A defensible default set: turns fog into something buildable · ships things people actually use · easy to work with across a seam. Replace any of them with something truer to your history.
Each message needs to land at least twice, in different answers. Plan where.
Built correctly, shipped on time, and usage was poor. The most useful story you own, because it's the only one that proves you measure adoption at all.
Covers — tell me about a failure · how do you drive adoption · a time you were wrong · the most common requirements mistake · if nothing is adopted in a year, what happened · what are you not good at
Usage, not effort. If you never measured it, say that — it's part of the lesson.
Something still in use long after you left it. The counterweight to story one, and the one that needs the hardest number.
Covers — sell me on something you built · how do you drive adoption · how do you measure success · walk me through an end-to-end delivery · what's your role after go-live
Two numbers beats one. The outcome measure alone can be true while nobody uses it.
A problem that arrived undefined — no agreed statement, no owner, no measure — and you produced something buildable. This is the closest analogue to the actual job.
Covers — most ambiguous problem you've handled · how do you know discovery is done · what would you do in week one · how do you quantify current-state cost · what does this role add
Someone requested a solution; you found the real problem underneath and built something different — ideally smaller.
Covers — a controller wants a dashboard · when is a dashboard the wrong answer · how do you get requirements from busy people · a stakeholder insists on their spreadsheet · how do you say no
Two hard requirements: you must have been wrong about something, and the other person must come out of it reasonable. A story where you were entirely right and they were difficult is the worst possible answer.
Covers — tell me about a conflict · what if you disagree with our design · a VP sponsors something low-value · influencing without authority · hardest feedback
Someone senior, committed to a position, who moved. What matters is the mechanism — what actually shifted them, which is rarely the analysis.
Covers — a time you changed someone's mind · influencing without authority · presenting to executives · a VP sponsors something low-value · scope creep
You had to tell someone the thing they wanted wasn't happening as specified — and you brought alternatives rather than just the problem.
Covers — what if it's infeasible · how do you say no · how do you handle scope creep · working with engineers you don't manage · presenting to executives
A process, a project, or a feature you argued out of existence. The rarest story most candidates don't have, and the one that most reads as senior.
Covers — automate, redesign or eliminate · how do you prioritise · build vs buy vs extend · what's overhyped · what would you do in ninety days
Explicitly in scope for this role, and the strategy lead will likely probe it. Needs to show judgment about why the original was wrong, not just that you changed it.
Covers — show me something you redesigned · how do you validate a design · what makes a good finance interface · how do you research with busy users · how do you prototype without engineering time
The story that maps most directly onto the job you're interviewing for. If you have one where the hand-off itself was the problem you fixed, use that.
Covers — where does your role start and stop · how would you run the hand-off · getting work done through people you don't manage · what would make you fail here · what does this role add
Check your ten against this. If a row has no story against it, that's the gap to fill next — those are the questions you'd be improvising.
| Question type | Primary story | Backup |
|---|---|---|
| Tell me about a failure | 1 · nobody used it | 5 · the conflict |
| A time you were wrong | 5 · the conflict | 1 · nobody used it |
| Driving adoption | 2 · the one that stuck | 1 · nobody used it |
| Handling ambiguity | 3 · fog into a spec | 8 · the thing you killed |
| Requirements craft | 4 · asked for the wrong thing | 3 · fog into a spec |
| Stakeholder management | 6 · changed a mind | 7 · the bad news |
| Saying no / prioritising | 7 · the bad news | 8 · the thing you killed |
| Judgment about what to build | 8 · the thing you killed | 4 · asked for the wrong thing |
| Design and UX | 9 · the redesign | 2 · the one that stuck |
| Working across teams | 10 · across a boundary | 7 · the bad news |
| End-to-end delivery | 2 · the one that stuck | 10 · across a boundary |
| Executive communication | 6 · changed a mind | 7 · the bad news |
The check before you stop
Read your ten back and ask: does at least half of them contain a real number, and does every single one contain something that didn't go perfectly? If the answer to either is no, you have a set of anecdotes rather than a story bank — and the difference is audible in the room.