STAR Interview Answer Builder from Messy Work Stories

Prompt

Act as an interview coach who has sat on hiring loops for ICs and managers. You turn messy stories into STAR answers that sound like the candidate, not a textbook. You do not invent metrics.

Inputs:
- Role I am interviewing for: [Role]
- Question I expect: [Question]
- Raw story: [Story]
- My actual part vs the team's: [Scope]
- Numbers I can stand behind: [Numbers]
- Time budget: [60 seconds / 90 seconds / 2 minutes]
- Voice: [Voice]
- Seniority signal I want: [IC craft / influence / leadership]
- Things I must not claim: [Must not]

Generate:
1. Story pick: In one sentence, is this the right story for the Question? If not, say which part of Story to use, or what missing fact would make it fit. Do not replace the story with a generic one.
2. STAR map: Situation, Task, Action (only what I did, per Scope), Result (only Numbers). Flag anything in Story that is team-credit or luck and keep it labeled.
3. Timed answer: Write the spoken answer at the requested Time budget. Short sentences. One concrete moment. Result in the last 2-3 lines. No "I leveraged synergies."
4. 30-second cut: Same story, half the time, for when they interrupt.
5. Failure / conflict variant: If the Question is about a miss, conflict, or "tell me about a time you were wrong," rewrite using the same facts. Do not turn a win into fake humility. If Story has no miss, say so and write a "what I would do differently" coda using only facts.
6. Follow-ups (6): Questions a good interviewer will ask next. For each, a 2-line honest answer from Inputs. If a follow-up would require a number you do not have, the answer is "I do not have that number; here is the proxy I do have."
7. Red flags to avoid: Phrases in the draft that sound coached, blamey, or inflated. Rewrite those lines.

Constraints:
- Do not invent revenue, headcount, percentages, titles, or quotes.
- I/we must match Scope. If the story is a team win, say what I owned.
- Ban: "passionate," "at the end of the day," "circle back," fake humility, dumping on a named coworker.
- Honor Must not.
- Spoken English, not an essay. Time budget is a hard cap.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Role I am interviewing for: Staff product manager, B2B workflow tool
Question I expect: Tell me about a time you influenced without authority
Raw story: Engineering wanted to rebuild the export pipeline (6 weeks). Sales wanted a CSV mapping UI for one enterprise trial (Northline, 58 seats) that was blocked on exports. I did not manage either team. I ran a 90-minute working session, pulled 12 real export files from support, and showed that 9 of 12 failed on one date-format bug, not on architecture. We shipped a 3-day fix plus a simple mapping screen. Trial converted. Rebuild was parked for a quarter.
My actual part vs the team's: I convened the session, pulled the files with support's help, wrote the one-pager, sat with the engineer on the date bug. I did not write the code. Sales owned the trial conversation.
Numbers I can stand behind: 12 files, 9 failed on date format, 3-day fix, 6-week rebuild estimate, 58-seat trial converted, rebuild parked for a quarter. I do not have revenue.
Time budget: 90 seconds
Voice: Direct, calm, no TED talk
Seniority signal I want: influence
Things I must not claim: that I saved the deal alone, that I managed eng, revenue numbers

Example Output

1. Story pick
Yes. The question is influence without authority. You had no reporting line and still changed a 6-week plan with evidence. Keep the date-format bug as the hinge, not the conversion as a personal trophy.

2. STAR map
Situation: Enterprise trial (Northline, 58 seats) blocked on exports. Eng wanted a 6-week rebuild. Sales wanted a mapping UI. You managed neither team.
Task: Unblock the trial without picking a tribe.
Action (yours): Convened a 90-minute session, pulled 12 real export files with support, showed 9/12 failed on one date-format bug, wrote the one-pager, sat with the engineer on that bug. Not your code. Not your sales call.
Result: 3-day fix plus a simple mapping screen. Trial converted. Rebuild parked for a quarter. No revenue number.

3. Timed answer (~90s)
"I needed two teams I do not manage to stop arguing about a rebuild. Sales had a 58-seat trial stuck on exports. Eng wanted six weeks to redo the pipeline. I asked support for real files, sat down for 90 minutes, and we looked at twelve exports. Nine failed on one date format, not on architecture. I wrote that up in a one-pager and sat with the engineer on the bug. They shipped a three-day fix and a thin mapping screen. The trial converted. We parked the rebuild for a quarter. I did not write the code and I did not own the sales thread. What I owned was the evidence and the room."

4. 30-second cut
"Trial blocked on exports. Eng wanted a six-week rebuild. I pulled twelve real files; nine failed on one date bug. I do not manage those teams. We did a three-day fix instead. Trial converted. Rebuild waited a quarter. I owned the evidence, not the code."

5. Failure / conflict variant
This story is a win. Honest coda: "What I would do differently: I would have pulled those twelve files before the rebuild estimate existed, so we never spent calendar time treating architecture as the first guess." Do not invent a blow-up with Eng.

6. Follow-ups
- "Who disagreed?" Eng wanted the rebuild; Sales wanted UI. I did not name people. I put files on the table.
- "What was your title power?" None. I convened. I did not assign work.
- "Revenue?" I do not have that number. Proxy: 58-seat trial converted.
- "What did you personally ship?" One-pager, session, pairing on the bug. Not the PR.
- "What if the bug had not been the cause?" Then the rebuild would have been the live option. The files were the test.
- "How did you keep trust with Eng?" I did not mock the rebuild. I said it could still happen; it was the wrong first cut.

7. Red flags
Avoid "I saved the deal." Use "the trial converted." Avoid "I led eng." Use "sat with the engineer." Avoid a fake percentage. Twelve and nine are the numbers.