In this guide
Begin with the capability being assessed
Listen for the skill inside the question: decision-making, leadership, conflict, customer focus, learning or execution. Clarify if needed. Choose an example that provides evidence of that capability at an appropriate level of complexity.
Do not force your favourite story into every question. The best example is relevant, recent enough to recall accurately and clear about your personal responsibility.
Build a bank of verified examples
Prepare examples from different roles and situations. Record the problem, stakeholders, your responsibility, action, outcome and lesson. Confirm dates, scope and measures you plan to mention.
Protect confidential information. Generalise identifying detail when appropriate and explain that you are doing so. Keep team results separate from your own contribution.
Use situation, task, action and result
The U.S. Office of Personnel Management includes the STAR model in its structured-interview guidance. Situation gives essential context. Task explains your responsibility. Action shows what you actually did and why. Result describes the outcome and evidence.
Keep situation and task concise so action receives enough time. Use ‘I’ for your decisions and ‘we’ for genuine team work.
Show judgement inside the action
A list of steps may show activity without revealing leadership. Explain the trade-off, information considered, people involved and reason for the choice. Mention what you ruled out when it helps the interviewer understand the decision.
Include communication and adjustment, not only the final move. Interviews often assess how you worked with constraints and other people.
Fictional answer spine
Situation: A regional rollout produced conflicting store reports.
Task: I was responsible for creating one reliable review before the next operating meeting.
Action: I compared definitions, involved two store managers, tested one exception format and documented unresolved figures.
Result: The meeting used one agreed view; I then added a definition check to future rollouts.
Describe results with honest precision
Use verified measures when they are appropriate to disclose. Otherwise describe the observable change: a decision made, process adopted, issue resolved or stakeholder response. Do not claim causation when several factors influenced the result.
Include an imperfect result when it demonstrates learning and accountability. Explain what you changed afterwards rather than disguising the limitation.
Adapt the story to the question and time
Prepare a short and full version of each example. Lead with the answer, then expand. Watch the interviewer’s cues and stop when the evidence is sufficient. A clear two-minute answer is stronger than a complete project history.
If a follow-up reveals missing detail, answer directly. Do not repeat the entire story. Ask whether the interviewer would like more context when the scope is complex.
Practise for accuracy, not performance
Rehearse aloud from bullet points rather than memorising a script. Ask a trusted listener which capability the story demonstrated and what your contribution appeared to be. Revise unclear evidence or ownership.
Before the interview, review role requirements and select likely examples. Afterwards, note questions that exposed gaps in your story bank. Keep the examples truthful as your career develops.
Before you move on
- The example matches the capability in the question.
- Dates, scope, measures and permissions have been checked.
- Situation and task are concise enough to leave room for action.
- My decisions and team contributions are clearly distinguished.
- The result is observable and does not overstate causation.
- Short and full versions are available for different time limits.
- Practice improves clarity without turning the answer into a script.
Sources and further reading
These official resources informed the guardrails and practical method in this guide.
This preview uses fictional examples where indicated. Read our editorial approach.