Interview prep - building a story bank from your proof

A story bank turns interview prep from memory panic into retrieval. You should not write a new answer from scratch for every behavioral question. Build a small set of truthful, flexible stories that can answer many prompts.

Start with six core stories:

1. A hard technical or product decision. 2. A conflict you owned. 3. A metric you moved. 4. A project you cut, simplified, or deprioritized. 5. A teammate, customer, or stakeholder you helped. 6. A failure you learned from.

For each story, write the STAR spine:

Situation: What was happening? Task: What were you responsible for? Action: What did you personally do? Result: What changed, and how do you know?

Example story spine:

Prompt: Tell me about a time you improved a process. Situation: Customer onboarding handoffs were inconsistent after sales close. Task: I owned the operating model between Sales, Customer Success, and Implementation. Action: I created a required intake form, weekly exception review, owner field, and launch-readiness dashboard. Result: Teams had one place to see blocker status, ownership, and next actions; onboarding reviews became more structured and less dependent on private Slack threads.

Now create three lengths:

30 seconds: Use for recruiter screens and quick prompts. State the problem, your action, and the result.

90 seconds: Use for hiring managers. Add constraints, tradeoffs, and collaboration details.

3 minutes: Use for deep loops. Include why you chose the approach, what almost failed, what you learned, and what you would do differently.

Story tagging:

Tag every story by competency: leadership, ambiguity, conflict, customer empathy, data, execution, technical judgment, communication, resilience, and prioritization. One story can carry several tags. The goal is coverage, not volume.

Practice prompts:

Tell me about a time you influenced without authority. Tell me about a time you had incomplete data. Tell me about a project that failed. Tell me about a disagreement with a stakeholder. Tell me about a time you had to move quickly. Tell me about your most measurable impact.

Checklist:

Each story is true and specific. Your personal contribution is clear. The result is concrete, even if it is qualitative. You can tell the story without reading it. You know which prompts each story can answer. You have at least one story that shows learning, not perfection.

Mistakes to avoid:

Do not memorize a script word-for-word. Memorize the spine. Do not use "we" for the whole answer. Name your role clearly. Do not pick only heroic wins. Interviewers often learn more from tradeoffs. Do not bury the result. Answerers often spend too long on context. Do not make every answer three minutes. Match the depth to the interviewer.

Where RoleWorth fits:

RoleWorth's evidence library can surface candidate stories from your resume, application kits, and prior role notes. For each opportunity, RoleWorth can suggest which stories map to the job's requirement spine, then help you rehearse concise versions before interviews.