Building a story bank

Do not memorize 40 thin anecdotes. Build 8–10 deep stories you can retarget to multiple questions. Map each story to 2–3 themes. Store them in a doc with bullets: context, your actions, metrics, principles covered, follow-up questions you might get.

This pairs naturally with a brag document. Update after big launches so the bank stays fresh.

Walking through the inventory

Suggested set:

1. Project you owned end to end (delivery + production)
2. Production incident or tough bug
3. Technical disagreement with a peer or lead
4. Ambiguous problem you scoped yourself
5. Time you said no / cut scope
6. Failure or missed deadline and recovery
7. Mentoring or unblocking someone
8. Cross-team dependency you drove
9. Customer / user impact story (support escalation, abuse, accessibility)
10. Initiative you started without being asked

You will not get novel prompts so much as remixes. Pre-map:

Reuse is fine across a loop day if you emphasize different facets — the same migration for Ownership with one interviewer and Disagree-and-Commit with another. Do not tell the identical five-minute monologue twice to the same panel if you can avoid it.

Practice methods that work:

1. Write the bank in bullets first.
2. Record two-minute answers on your phone; cut fluff.
3. Do mock sessions where the interviewer digs ("What did you do next?" "What were the metrics?").
4. Prepare 30-second and 5-minute versions of each story.
5. Practice the elevator version of your career arc for "tell me about yourself."

Deep dives are normal. If you only memorized a polished paragraph, follow-ups will break you. Know the dates, the alternatives you rejected and the names of systems involved.

Common mistakes

• Forty thin stories. You cannot survive a "what alternatives did you consider?"
• Identical monologue twice. Change the facet, or pick another story.
• Bank that froze two years ago. Update after launches; interviewing is editing.

Check yourself

1. A prompt is "tell me about unclear requirements." Which story do you reach for?

The one you already tagged as ambiguity / scoping — not a new invention in the chair.

2. Why 8–10 deep stories instead of 40 short ones?

Deep stories survive follow-ups: alternatives, metrics, names of systems. Thin anecdotes die on the first probe.

Key takeaways

• Eight to ten deep stories, each mapped to two or three themes.
• Pre-map prompt shapes so remixes do not surprise you.
• Rehearse out loud; keep short and long versions.

Further learning

Next: signaling level with stories.