Cruxly › Behavioral › Answering Well

Building a Story Bank

eight stories, each covering several questions

You cannot prepare an answer per question — there are hundreds of questions. You prepare a small set of rich stories and learn to aim each one at several. Eight is enough for almost any loop.

Why eight, and why rich

Interviewers draw from a large pool of prompts, but the prompts map onto a much smaller set of underlying competencies. A story rich enough — with conflict, a hard call, a mistake, and a measurable outcome — can legitimately answer six or seven different prompts by emphasising a different part.

One project where you disagreed with a tech lead, shipped under pressure, made a call with incomplete information, and later found a flaw in your own decision can answer: tell me about a conflict, a time you influenced without authority, a decision with incomplete data, a time you were wrong, a time you delivered under pressure, and your most significant technical contribution.

So do not hunt for more stories. Mine the ones you have for more angles. Depth beats breadth: an interviewer who probes a story you know in detail finds more substance, and probing is exactly what they will do.

The coverage grid

Draw a grid: your stories down the side, these competencies across the top.

Ownership — you took responsibility beyond your remit. Conflict — you disagreed with someone and resolved it. Failure — you got something wrong and it had consequences. Ambiguity — you decided without enough information. Influence — you changed minds without authority. Pressure — you delivered against a hard constraint. Growth — you were bad at something and got better. Collaboration — you made someone else more effective.

Mark which stories cover which cells. Two things will be obvious immediately: some stories cover five cells, and one or two columns are empty.

Empty columns are your actual preparation. Almost everyone is missing Failure with real consequences (because it is uncomfortable), Growth (because it requires admitting a weakness), and Collaboration-where-you-helped-someone-else (because it does not feel like an achievement). Go and find those. An empty column is a question you will be asked and will answer badly.

Write the facts, not the script

For each story, half a page:

Context — team, timeframe, your role.
The names — real first names. Recalling "Priya" is faster than reconstructing "a colleague on the platform team" mid-sentence, and specificity is itself a credibility signal.
The numbers — duration, size, error rate, before and after. Look them up now; you will not remember them under pressure, and a vague number invites a probe you cannot answer.
The three or four decisions you made, with the reason for each.
What went wrong, including anything that was your fault.
The result, honestly, including what did not work.
The lesson, and what you have done differently since.
Which competencies it can serve.

Write facts, not sentences. A written-out answer gets memorised and delivered flatly, and it collapses the moment the question is phrased differently. Facts get assembled fresh each time, which sounds like what it is: someone who was there.

Aiming one story at different questions

Same story, different emphasis. The Situation and Result barely change; the Action beat is re-weighted and the Reflection is re-pointed.

Take the payments migration:

Asked about conflict: the Action foregrounds the argument with your tech lead about the two-week dual-write cost, how you made the case, and what you conceded.
Asked about ownership: it foregrounds you noticing the reconciliation gap nobody owned, and taking it.
Asked about ambiguity: it foregrounds the decision to cut over early on nine days of clean data, and how you judged nine days was enough.
Asked about failure: it foregrounds building reconciliation in week three instead of week one, and what that cost.

Practise the switch explicitly. Take one story and tell it four ways out loud. The first time it will feel like the same story with the label changed, which is the thing to fix: the evidence must change, not just the framing sentence.

Choosing well under pressure

When the question lands, spend three seconds choosing. Say "let me think of a good example" out loud — it buys you the time and it reads as care rather than hesitation.

Pick by three tests:

Tension. Was it actually hard? A smooth project is unscoreable.
Agency. Did you make decisions? A story where you executed someone else's plan well has nothing in it for this round.
Recency and recall. Prefer the last two or three years, and prefer a story you can be probed on. An impressive story you half-remember falls apart on the second follow-up, and the second follow-up always comes.

Do not reuse one story across a whole loop if interviewers compare notes — and at most companies they do. Spread them. This is another reason eight is the number: a four-interview loop with two stories each needs exactly that.

A note on confidentiality. You can tell these stories without naming employers' unreleased products or leaking numbers you should not. "A large internal service, call it the billing pipeline" works. Being visibly careful about this is itself a positive signal — interviewers notice a candidate who handles their previous employer's information well, because they are about to become your previous employer.

How to say it in the interview

"I keep a short set of stories I know well, each with the facts written down. Under pressure I am recalling a story I have, not inventing one."

Checklist

Have at least eight distinct stories written down
Mapped stories against competencies in a grid
Found a failure story with real consequences
Wrote down real names and real numbers for each story
Recorded the decisions and their reasons, not a narrative script
Practised telling one story aimed at four different questions
Included what went wrong and what was your fault in each
Chose stories with real tension and real agency in them

Practice this interactively