Verified against ChatGPT · 2026-08-13
Build a reusable STAR story bank from your real work history that flexes to different behavioral questions
Turns your actual career moments into a small set of STAR stories built to be reusable across many different behavioral questions, with explicit notes on which question angles each story can flex to answer.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Help me build a STAR story bank from my real career moments — a small set of stories I can flex across many different behavioral interview questions, rather than one story per question I might get asked.
MOMENTS FROM MY CAREER I THINK ARE STRONG STORY MATERIAL
1) Rebuilt a broken onboarding process after a bad launch, 2) disagreed with my manager about a vendor choice and turned out right, 3) took over a project mid-stream after the previous owner left, 4) mentored a junior hire who almost quit in their first month.
COMMON BEHAVIORAL THEMES I EXPECT TO BE ASKED ABOUT
Leadership, conflict/disagreement with authority, ambiguity/ownership, mentorship, handling failure.
How many distinct stories: aim for 4-5 stories that together cover the themes I listed, not one story per theme — a single strong story often demonstrates 2-3 different competencies depending on which part of it you emphasize.
For each of my career moments, build it out as:
SITUATION — one or two sentences of real context, specific enough to be credible, not generic.
TASK — what I was actually responsible for, stated so it's clear what decision or ownership was mine versus the team's.
ACTION — the specific choices I made, in enough detail that a follow-up question ("why did you choose that approach over the alternative") has a real answer available, not just an outcome-first summary that skips the reasoning.
RESULT — the actual outcome, including anything imperfect about it — a result that's suspiciously perfect reads as embellished, and naming a real trade-off or limitation makes the story more credible, not less.
After each story, list which of my expected themes it can answer, and for each theme it covers, one sentence on which part of the story to emphasize or lead with to make it land as an answer to that specific theme rather than reading as the same story told the same way regardless of what was asked.
WHAT NOT TO DO
Do not invent details, outcomes, or numbers I didn't give you — if a story is missing a concrete result, ask me for it rather than filling in a plausible-sounding one. Do not force a story to cover a theme it doesn't genuinely fit; tell me instead if one of my expected themes has no strong story in the set and needs new material.
End with a coverage map: my expected themes down one side, my stories across the top, marked where each story covers each theme.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Building one story per anticipated question is a losing strategy because behavioral interview question banks are effectively infinite in surface phrasing while the underlying competencies they test are a small, stable set — leadership, conflict, ambiguity, failure recovery — which means a well-built small set of stories that each flex across several competencies covers far more ground than a large set of narrow, single-purpose ones, and is also easier to actually keep fresh in memory under interview pressure. The instruction to build 4-5 flexible stories rather than one-per-theme forces the model to identify which real moments in the candidate's history are naturally rich enough to support multiple competencies depending on emphasis, which is a genuine skill difference from just categorizing moments into single boxes. Requiring the Action section to include the reasoning behind a choice, not just the choice and its outcome, matters because a competent interviewer's most revealing follow-up question is almost always "why did you do it that way instead of the alternative," and a candidate whose STAR prep only covers the outcome-level story has nothing prepared for that follow-up, which is exactly the moment a rehearsed-sounding story starts to visibly fall apart. The instruction to preserve an imperfect result rather than polish it into a clean win addresses a subtle credibility problem: STAR stories that resolve too neatly, with every outcome unambiguously positive and every number suspiciously round, read to experienced interviewers as embellished or cherry-picked, while a story that names a real trade-off or partial result reads as something that actually happened. The refusal to invent missing details protects the candidate from the single worst outcome in interview prep — being caught contradicting a detail the candidate never actually said but the model fabricated to fill a gap, which is far worse for credibility than simply not having a number ready.
What you get back
Story 2 (vendor disagreement): covers 'conflict/disagreement with authority' and 'ownership.' For the conflict theme, lead with the specific moment you pushed back and what evidence you brought, not the eventual vindication — the vindication should land as the Result, not be foreshadowed early, since interviewers are testing how you handled the disagreement in the moment, not whether you were later proven right.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
