Organize information

Turn an experience into a STAR interview story

Structure a truthful story around personal action, evidence, trade-offs, and learning

6 min setupTested with:ChatGPTReviewed: 2026-08-28
1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Turn the verified experience into a spoken STAR interview answer.

Context, goal, constraints, team roles, exact actions, decisions, results, setbacks, and evidence:
[experience]

Interview question and assessed competency:
[question]

Time limit, role level, confidentiality, weak points, language, and prohibited claims:
[constraints]

Use only supplied facts. Keep Situation and Task brief; devote most time to the candidate's own Actions, reasoning, alternatives, communication, and adaptation. Separate personal contribution from team work and preserve uncertainty, setbacks, and concurrent factors. Result may be qualitative; do not invent a metric or claim causality. Include relevant reflection without manufacturing a perfect lesson. Return a timed spoken answer, STAR evidence map, shorter version, likely follow-up questions with truthful answers or missing-detail prompts, and phrases that overclaim ownership or impact.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Raw experience
Retail supervisor. Weekly rotas for 45 employees generated frequent corrections. Store managers owned availability data. I proposed and built an Excel workbook with Tables, XLOOKUP, SUMIFS and validation, tested it on one week, found that duplicate employee IDs caused wrong lookups, added a uniqueness check, then trained two supervisors. I maintained it. Correction logs averaged 12/month for three prior months and 5/month for three later months. Staffing policy also changed, so contribution cannot be isolated. One supervisor initially preferred the old sheet; I asked them to test two shifts and used their feedback to simplify the input tab.
Interview question and competency
Tell me about a time you improved a process. Competency: diagnosing a problem, using data, involving users, and sustaining a practical change.
Answer constraints
90 seconds, Operations Analyst interview, UK English. Do not say I led a team, reduced corrections by a percentage, or caused the full reduction. Employee data details are confidential. Weak point: no formal experiment.

Example output

Situation and task, about 15 seconds: “In my retail-supervisor role, weekly rotas for 45 employees needed frequent correction. I wanted to make the input and checking process more reliable without changing managers' ownership of availability data.”

Action, about 50 seconds: “I first reviewed the correction pattern and mapped where data entered the rota. I proposed an Excel workbook using Tables, XLOOKUP, SUMIFS and validation, then tested it on one week rather than replacing the existing sheet immediately. The test exposed duplicate employee IDs causing incorrect lookups, so I added a uniqueness check before wider use. I trained two supervisors and maintained the workbook. When one preferred the old sheet, I asked them to test two shifts and used their feedback to simplify the input tab.”

Result/reflection, about 25 seconds: “Correction logs averaged 12 per month in the three months before and 5 in the next three. A staffing-policy change happened at the same time, so I would not attribute the full difference to the workbook. The useful lesson was to pilot the control with real users and treat resistance as workflow evidence; the duplicate-ID test became part of the ongoing check.”

Follow-up on measurement: no controlled comparison was run; logs and concurrent policy are the evidence limits. Avoid “I transformed scheduling” or “my system cut errors.”

Why this works

  1. 1

    Action-heavy structure gives interviewers evidence of behavior rather than a polished team outcome.

  2. 2

    Ownership and concurrency checks prevent STAR structure from creating false personal causality.

Check the result

  • Does most of the answer explain the candidate's actual decisions and actions?

  • Are team ownership, setbacks, concurrent factors, and evidence limits explicit?

  • Can every result and reflection be defended under follow-up questions?

More ways to explore

Where this recipe fits

Text promptsCareer & job searchChatGPT prompts

Keep the work moving

Write & communicate 5 min setup

Turn real experience into resume bullets

Express verified scope, action, method, and result without inflating ownership or inventing metrics

Evidence-backed resume bullets, fact checks, variants, and missing-detail questions
Open recipe