Building a Story Bank
This section works both sides of the table. For candidates: how to build a bank of stories that covers any interview. For interviewers: how to build a bank of great questions mapped to your principles. Both banks make you better at your job.
The candidate's story bank
Why 6-8 stories cover most interviews
Most behavioral interviews ask 3-5 questions. But you don't need a unique story for each question — a single well-chosen story can demonstrate 2-3 principles simultaneously. With 6-8 strong stories, you can answer almost any behavioral question by selecting the story that best fits.
| Number of stories | Coverage |
|---|---|
| 2-3 | Thin. You'll stretch the same story across very different questions. |
| 6-8 | Sweet spot. Enough variety to match most questions without over-preparing. |
| 15+ | Diminishing returns. Too many stories means none are deeply prepared. |
Mining your experience
Stories come from five categories of experience:
| Category | Examples | Why it's rich |
|---|---|---|
| Projects | Launches, migrations, redesigns, greenfield builds | Every project has decisions, tradeoffs, and results |
| Conflicts | Disagreements with peers, pushback from leadership, cross-team friction | Reveals collaboration, influence, and judgment under pressure |
| Failures | Missed deadlines, broken production, wrong technical bets | Shows self-awareness, learning, and ownership |
| Mentoring | Onboarding new hires, coaching underperformers, growing junior engineers | Demonstrates leadership and communication |
| Pivots | Changing direction mid-project, adapting to new constraints, learning a new domain | Shows adaptability, judgment, and learning velocity |
The story-to-principle matrix
Map each story to the principles it demonstrates. One story should cover 2-3 principles:
| Story | Ownership | Collaboration | Customer Focus | Bias for Action | Dive Deep |
|---|---|---|---|---|---|
| Payment monitoring system | ✓ | ✓ | ✓ | ✓ | |
| Cross-team API redesign | ✓ | ✓ | ✓ | ||
| Production incident response | ✓ | ✓ | ✓ | ✓ | |
| Mentoring struggling junior | ✓ | ||||
| Pivoting mid-sprint on new data | ✓ | ✓ | |||
| Legacy system migration | ✓ | ✓ | ✓ |
The gap check: If a principle has no stories mapped to it, you need to find or develop one. If a story only maps to one principle, consider whether there's a richer story in your experience.
Keeping stories fresh
- Update quarterly: Review your bank and swap in recent, more impressive examples
- Add depth over time: Each time you tell a story, note what resonated and what questions came up — add those details to your preparation
- Retire old stories: If a project was 5+ years ago and you have better examples, let it go
The interviewer's question bank
Why interviewers need a bank too
Preparing questions 5 minutes before an interview leads to mediocre questions. A curated bank of proven questions — organized by principle, tested over multiple interviews — is far more effective.
Building your question bank
For each principle you regularly evaluate, maintain 3-4 strong questions:
| Principle | Primary question | Backup questions |
|---|---|---|
| Ownership | "Tell me about a time you took on something important that wasn't your responsibility." | "Tell me about a time you saw a problem nobody was addressing. What did you do?" / "Describe a time you went beyond your job description because the work needed to be done." |
| Collaboration | "Tell me about a time you needed buy-in from people who didn't report to you." | "Describe a time you had to resolve a significant disagreement with a colleague." / "Tell me about a cross-team project where you had to align competing priorities." |
| Customer Focus | "Tell me about a time you changed your approach because of something you learned from users." | "Describe a decision where you chose the user's interest over internal convenience." / "Tell me about a time you had to balance customer needs against technical constraints." |
| Bias for Action | "Tell me about a time you made a significant decision without complete information." | "Describe a time you had to move quickly on a decision. How did you decide what was 'enough' information?" / "Tell me about a time you chose speed over perfection. How did it turn out?" |
When to use backup questions
- Your primary question doesn't fit the candidate's experience
- The candidate already covered that scenario in an earlier interview (check the loop plan)
- You want to evaluate the same principle from a different angle
Iterating on your questions
After every interview loop, review which questions generated the best signal:
- Strong signal: The candidate gave a detailed, probing-worthy answer with clear STAR elements
- Weak signal: The candidate gave a generic answer, or the question was too specific for their experience
- No signal: The candidate couldn't think of a relevant example (question too narrow) or went off-topic (question too vague)
Retire weak questions. Promote strong ones. Your bank improves with every loop.
Exercise: Build both banks
Part 1: Build your candidate story bank
Use the guided builder below to create your personal story bank. It will walk you through each STAR component, help you map stories to principles, and flag any gaps in your coverage. When you're done, export the CSV to practice with offline.
Your story bank is empty.
Click + Add Story to start building. We'll walk you through it step by step.
Part 2: Interviewer question bank
Pick 2 principles you evaluate most often and write a primary + backup question for each.
Choose 2 principles. For each, write a primary interview question and one backup question. Both should be behavioral, open enough for any candidate, and targeted at the specific principle.
Remember from Workshop 201: great questions let candidates show their best story, target a specific principle without naming it, and lead to 15+ minute conversations with natural probing paths.
This exercise supports AI-powered coaching via Claude. Enter your access code to enable it, or use the offline feedback below.
Why is 6-8 stories the sweet spot for a candidate's story bank?
As an interviewer, when should you use a backup question instead of your primary?
You notice that all 4 of your prepared stories are about successful projects with great outcomes. What's the problem?