What belongs in each part?

Situation: establish the setting and the problem. Task: explain what you were responsible for. Action: describe what you actually did and why. Result: explain what changed, what remained unresolved, or what you learned.

The letters are a planning tool. You do not need to announce them in the interview. Give the listener enough context to understand your choices, then spend most of your explanation on those choices. A long history of the company usually adds less than one concrete decision.

A worked example: resolving a handover problem

Fictional example for practice, not a customer story.

“Our support team was receiving tickets without enough information to act. I was responsible for improving the handover from sales. I reviewed recent tickets, asked both teams where information was getting lost, and drafted a short checklist. We tested it together for a week and removed fields that nobody used. The next group of tickets needed fewer follow-up questions, although I did not track an exact percentage. We kept the checklist and assigned someone to update it.”

The answer identifies a problem, a personal responsibility, specific actions, and an observable outcome. It also admits a measurement limit. If this were your experience, be ready to explain which checklist fields mattered, how you handled disagreement, and how you knew the handover had improved.

Build an evidence bank before writing answers

Choose four real experiences: a problem you solved, a disagreement you handled, a mistake you corrected, and a piece of work you are proud of. Work, study, volunteering, and personal projects can all provide examples when they are relevant to the role.

  • What happened, and why did it matter?
  • What was my responsibility rather than the team's overall goal?
  • Which two or three actions did I personally take?
  • What evidence supports the outcome?
  • What would I do differently now?

Keep confidential names, client details, and internal figures out of your notes. You can explain a decision without revealing protected information. Use approved or non-confidential measures where available.

Fix the three most common weaknesses

Too much “we”: acknowledge the team, then identify your contribution. No result: describe a verified outcome or a lesson you put into practice. Invented precision: do not add a percentage because the answer sounds stronger with one. An honest qualitative result is better than an unsupported metric.

For a failure question, the result does not have to become a success story. Explain the impact, your responsibility, and the change you made afterward. Avoid blaming other people or claiming a perfect outcome that your actions could not have produced.

Practice for follow-up questions

Speak the answer aloud once, then try it again from five bullet points. Ask a practice partner: “What did you understand my contribution to be?” If they cannot tell, sharpen the action section. Then rehearse one follow-up: “Why did you choose that approach?” That tests understanding more usefully than memorizing every word.

STAR suits questions about a specific past event. For a broad introduction, use the structure in our guide to “Tell me about yourself.”