STAR stands for Situation, Task, Action and Result. It gives you a sequence for explaining a specific experience when an interviewer asks about something you have done. The Open University describes it as a way to organise examples for interviews. The structure helps a listener follow your evidence; it does not replace the evidence.
Choose an experience you can discuss truthfully. Paid work, a class project, volunteering or another relevant activity can provide a usable example. You do not need a dramatic rescue story or a fabricated percentage to explain what you did and what happened.
Decide which experience answers this question
Underline the ability the interviewer is asking about: resolving a disagreement, organising competing tasks, learning something unfamiliar or taking responsibility for an error. Choose one experience that gives you evidence of that ability. A story about your busiest week may be memorable but irrelevant to a question about handling feedback.
Before turning it into polished sentences, note the facts: who was involved, what you were responsible for, what you actually did and what you observed afterwards. If a detail is confidential, choose a safe level of description or a different example. Keep the original facts available while rehearsing so editing does not quietly improve the story beyond what happened.
Give each part of STAR a useful job
Situation provides the context needed to understand the event. Task names your responsibility or the outcome you were asked to work toward. Action explains your own choices and work. Result describes what happened as a consequence, including a limitation or lesson when appropriate. Avoid using the whole answer to explain the background and leaving your action as “we handled it.”
Write the action with specific verbs: compared, asked, tested, reorganised, explained or followed up. Those verbs still need an object and a reason. “I reorganised the checklist so each task had an owner” tells the listener more than “I showed great leadership.” Then connect the result to evidence you can reasonably describe.
Separate your contribution from the team result
You can acknowledge collaboration and still make your role clear. Say what the team needed to achieve, then distinguish your own action from decisions made by others. “Our team completed the event; I checked the room bookings and created the updated setup list” is more precise than taking ownership of every part of the outcome.
If you use a number, know where it comes from. If you do not have a reliable measurement, describe an observed outcome without manufacturing one: the reviewer accepted the revised draft, the handoff was completed, or the same missing information stopped recurring in the records you reviewed. Do not turn a limited observation into a company-wide improvement claim.
Handle a result that was incomplete or unsuccessful
Some questions ask about mistakes or difficult situations. A useful answer can state what did not work, the correction you made and what you would check earlier next time. Keep the account specific and proportionate. Saying that everything was secretly a success can make the explanation harder to assess.
For a task still in progress, state the current outcome and avoid borrowing the expected future result. Explain what you have verified and what is not yet known. The point is to present an honest account of your reasoning and work, not to make every experience end with an impressive metric.
Rehearse the story instead of memorising a script
Use four short bullet prompts to remember the sequence, then answer aloud in your own words. Check whether the listener can tell what the task was, what you did and how you know the result. If the answer is too long for the conversation, remove background details that do not explain your choices.
Prepare for a follow-up about a decision or an alternative. Being able to answer that follow-up from real facts is more useful than perfect wording. The fictional example here demonstrates structure only; it is not an experience to claim as your own or a prediction of hiring success.
Start with this workflow.
- Choose a relevant real event
Match the requested ability to evidence you can explain truthfully and safely.
- Map context, responsibility, action and result
Keep your contribution distinct from the team’s work and label uncertain details.
- Rehearse and check the evidence
Say the answer aloud, trim unnecessary background and prepare for a follow-up about your choices.
WORKED EXAMPLE
A clear account of coordinating a student project
Fictional example for practising structure: a student team is preparing a presentation and two people are editing the same section.
STARTING POINTI am a strong leader and solved all the team problems, so our presentation was a huge success.
AFTER CHECKINGSituation: our group had overlapping edits near the presentation deadline. Task: I was responsible for assembling the final slides. Action: I asked the two editors to agree on one version, listed the unresolved points and assigned each remaining section an owner. Result: we assembled one consistent deck before the deadline. I learned to agree ownership earlier; I do not have a measured effect on the final grade.
What changed
The answer names a responsibility and observable actions. It avoids claiming every team outcome or inventing a quantitative result.
Make your own working brief.
Question and requested ability: Real experience: Situation needed for context: My task or responsibility: My specific actions and reasons: Other people’s contributions: Observed result and evidence: Limit or lesson: Details I must keep confidential: Likely follow-up question:
Further reading.
This source supports the STAR structure. The student-project example and rehearsal worksheets are original teaching examples, not accounts of a real candidate.
