What is a story bank for behavioral interviews?

A story bank is a small set of prepared, true stories from your own experience — usually six to eight — that between them cover every kind of behavioral question, instead of a separate memorized answer for each question. The insight it rests on is that behavioral questions cluster into a handful of competencies (initiative, conflict, failure, customer focus, and so on), and a single well-lived story usually speaks to two or three of them depending on which facet you lead with. So rather than write forty brittle scripts, you build a handful of stories, prep each one for depth — a headline, two or three key moments, and detail held in reserve for follow-ups — and map them across the competencies until every question has a home. It beats memorization because a behavioral interview is a probe, not a quiz: the interviewer digs under your answer with “why did you decide that?” and “what did they think?”, and a story you actually lived has depth all the way down where a script hits bottom on the second follow-up.

How many stories do you need for a behavioral interview?

Six to eight is the working number for most engineering loops. That is enough to cover the nine competency families with two or three stories apiece — the coverage you want so that losing one story to nerves does not black out a whole family, and so no single story is stretched across so many questions that an interviewer wears it thin by probing it from every angle. Fewer than six and you start leaving gaps or over-relying on one heroic story; many more than eight and you cannot keep them all rehearsed to the depth that makes them worth telling. The number matters less than the coverage: the real test is whether, laid against the families, every family is covered at least once (ideally twice) and no story is doing the work of four. The coverage matrix on this page is built to show you exactly that picture for your own bank.

What competencies do behavioral interviews test?

Underneath the phrasing, behavioral questions probe a stable set of competencies: taking initiative, delivering under a deadline, problem-solving and deep dives, earning trust and handling conflict, learning and growth (the failure story), customer or user focus, innovation and creative solutions, developing others, and strategic thinking or leading without authority. Companies name and weight these differently — Amazon publishes sixteen Leadership Principles like “Dive Deep,” “Earn Trust,” and “Bias for Action,” and states that “we use our Leadership Principles every day, whether we’re discussing ideas for new projects or deciding on the best way to solve a problem” — but the underlying families are the same because they are the traits a team actually needs. The practical move is to build stories that cover these families, then relabel them to match whichever company’s value list you are interviewing against.

How do you answer “tell me about yourself” or “what’s your biggest weakness”?

These belong to a separate group of about six questions that get asked head-on and rarely probed, so the answer itself is the whole game — different rules from the story families. For “tell me about yourself,” use a power-of-three shape: three defining elements that add up to why you’re the right fit for this specific room, each a sentence, landing on the role — never a chronological walk through your resume, which they already have. For “biggest weakness,” name a real limitation, ground it in a moment it actually cost you, and say the concrete thing you’re doing about it now; the disguised strength (“I’m a perfectionist”) fails on contact because companies want genuine learning moments, not polished non-answers. The others in this group — a project you’re proud of, why this company, questions for the interviewer, and your career story — each have their own trap to avoid, laid out as attempt-before-peek cards on the page.

The Story Bank

You don’t memorize forty behavioral answers — you build six to eight true stories that between them cover every question a panel can throw, and rehearse until the right one comes to hand on reflex. A drill surface: the nine competency families as attempt-before-peek cards (how each is asked, what the interviewer greps for, the pitfalls, a fill-in scaffold), the six direct questions with different rules, a commit-first drill on the first sentence out of your mouth, and the signature — a live coverage matrix where you map your stories against the nine families and watch it flag the gaps and the one story doing too much.

Concept · Interview Craft. The source ↗

A free, interactive, animated visual explainer of The Story Bank — built to be understood, not skimmed.

Questions

What is a story bank for behavioral interviews?: A story bank is a small set of prepared, true stories from your own experience — usually six to eight — that between them cover every kind of behavioral question, instead of a separate memorized answer for each question. The insight it rests on is that behavioral questions cluster into a handful of competencies (initiative, conflict, failure, customer focus, and so on), and a single well-lived story usually speaks to two or three of them depending on which facet you lead with. So rather than write forty brittle scripts, you build a handful of stories, prep each one for depth — a headline, two or three key moments, and detail held in reserve for follow-ups — and map them across the competencies until every question has a home. It beats memorization because a behavioral interview is a probe, not a quiz: the interviewer digs under your answer with “why did you decide that?” and “what did they think?”, and a story you actually lived has depth all the way down where a script hits bottom on the second follow-up.
How many stories do you need for a behavioral interview?: Six to eight is the working number for most engineering loops. That is enough to cover the nine competency families with two or three stories apiece — the coverage you want so that losing one story to nerves does not black out a whole family, and so no single story is stretched across so many questions that an interviewer wears it thin by probing it from every angle. Fewer than six and you start leaving gaps or over-relying on one heroic story; many more than eight and you cannot keep them all rehearsed to the depth that makes them worth telling. The number matters less than the coverage: the real test is whether, laid against the families, every family is covered at least once (ideally twice) and no story is doing the work of four. The coverage matrix on this page is built to show you exactly that picture for your own bank.
What competencies do behavioral interviews test?: Underneath the phrasing, behavioral questions probe a stable set of competencies: taking initiative, delivering under a deadline, problem-solving and deep dives, earning trust and handling conflict, learning and growth (the failure story), customer or user focus, innovation and creative solutions, developing others, and strategic thinking or leading without authority. Companies name and weight these differently — Amazon publishes sixteen Leadership Principles like “Dive Deep,” “Earn Trust,” and “Bias for Action,” and states that “we use our Leadership Principles every day, whether we’re discussing ideas for new projects or deciding on the best way to solve a problem” — but the underlying families are the same because they are the traits a team actually needs. The practical move is to build stories that cover these families, then relabel them to match whichever company’s value list you are interviewing against.
How do you answer “tell me about yourself” or “what’s your biggest weakness”?: These belong to a separate group of about six questions that get asked head-on and rarely probed, so the answer itself is the whole game — different rules from the story families. For “tell me about yourself,” use a power-of-three shape: three defining elements that add up to why you’re the right fit for this specific room, each a sentence, landing on the role — never a chronological walk through your resume, which they already have. For “biggest weakness,” name a real limitation, ground it in a moment it actually cost you, and say the concrete thing you’re doing about it now; the disguised strength (“I’m a perfectionist”) fails on contact because companies want genuine learning moments, not polished non-answers. The others in this group — a project you’re proud of, why this company, questions for the interviewer, and your career story — each have their own trap to avoid, laid out as attempt-before-peek cards on the page.

The Story Bank

Questions

Related explainers