build-an-interview-story-bank

name	build-an-interview-story-bank
category	get-hired
description	Build a reusable bank of truthful interview examples mapped to competencies, personal contribution, evidence, and learning. Use when interview preparation needs breadth without memorized or inflated answers.

build-an-interview-story-bank

Preserve enough context to tell the truth under follow-up.

When to use

• Use for behavioral, manager, technical, case, promotion, or panel interviews.
• Do not combine events into a fictional story or claim team outcomes as individual work.

Procedure

1. Inventory projects, decisions, conflicts, failures, improvements, learning, service, and leadership across paid and unpaid work.
2. Capture situation, stakes, constraints, personal role, collaborators, actions, result, evidence, and later learning for each event.
3. Mark confidential details and create safe language that preserves meaning without exposing protected information.
4. Map stories to role competencies and identify gaps needing a different real example.
5. Add evidence such as metric definitions, dates, artifacts, feedback, or observable change; label estimates.
6. Prepare 30-second, two-minute, and deep versions without changing the facts.
7. Practice likely follow-ups about alternatives, disagreement, mistakes, tradeoffs, and personal contribution.
8. Keep one failure or weak-result story with genuine accountability and changed behavior.
9. Retire stale examples when dates, details, or permissions cannot be verified.

Failure plan

• If a detail is uncertain, say so or verify it rather than filling the gap.
• If confidentiality prevents a useful answer, state the boundary and use another example.

Done

• A story bank maps verified examples to competencies, evidence, personal contribution, collaborators, limitations, and learning
• Practice confirms each example remains consistent across short, full, and follow-up versions