STAR Interview Technique: Complete Guide & Worked Examples
The definitive guide to the STAR method — how to structure every competency answer, what interviewers are actually scoring, 8 fully worked examples, and the most common mistakes that sink otherwise strong candidates.
What is the STAR Interview Method?
STAR is a structured framework for answering competency-based interview questions — the "Tell me about a time when…" format used in almost every professional interview. STAR stands for:
| Letter | Element | What to Cover | % of Your Answer |
|---|---|---|---|
| S | Situation | Brief context — where, when, what was the setting? (1–2 sentences) | 10% |
| T | Task | What was your specific responsibility or challenge? (1–2 sentences) | 15% |
| A | Action | What did YOU specifically do? (3–5 concrete steps you personally took) | 55% |
| R | Result | What happened? Quantify wherever possible. What did you learn? | 20% |
Interviewers are not scoring your Situation or Task — they already know those before you finish describing them. They are scoring your Actions: what you personally chose to do, how you thought through the problem, and what specific skills you applied. A STAR answer where Action takes less than 40% of the total response is almost always a weak answer, regardless of the context or result.
Breaking Down Each Element
Situation — Set the Scene Quickly
Give enough context that the interviewer understands where and what, but don't over-explain. Interviewers don't need a full backstory — they need the minimum context to understand why the challenge existed.
Good: "During my second year at university, I was elected president of the Finance Society with a 40-person team and a £8,000 annual budget."
Too long: "So in my second year, I'd been involved in the Finance Society since first year and over time I got to know a lot of the members and they suggested I should run for president and I thought about it for a while and decided to go for it and then I won the election and…"
Task — Be Specific About Your Responsibility
Distinguish between what the group or team was trying to achieve, and what specifically was YOUR role. Interviewers are looking for individual contribution, not team outcomes. Use "I" not "we" in the Task description.
Action — This is the Core of Your Answer
This is where most candidates underprepare. Strong Action sections have three characteristics:
- Specific steps YOU took — not what the team did, not what happened passively. "I decided to…", "I approached the problem by…", "I chose to…"
- The reasoning behind your choices — why did you take that specific action? What were you trying to achieve? What alternatives did you consider?
- Skills and qualities demonstrated — analytical thinking, communication, leadership, resilience. Interviewers want to see the competency in action, not just hear that you "showed leadership."
Result — Quantify and Reflect
Strong results are specific and, wherever possible, quantified. "The project was successful" is weak. "We raised £12,000 — 50% above our original target — which funded three new initiatives" is strong. Even if the outcome wasn't fully positive, a mature reflection on what you learned turns a weak result into evidence of growth mindset.
Before any interview, prepare 6–8 strong STAR examples from your experience — work, university, volunteering, sport, societies. Each example should be versatile enough to demonstrate 2–3 different competencies depending on which element you emphasise. Map your bank against the employer's competency framework. For Amazon, map to their 14 Leadership Principles. For consulting, map to analytical thinking, communication, and leadership.
Common Competency Questions by Theme
| Competency Theme | Common Question Phrasings | What Employers Are Scoring |
|---|---|---|
| Leadership | "Tell me about a time you led a team." / "When did you motivate others to achieve a goal?" | Initiative, direction-setting, influencing without authority, team coordination |
| Teamwork | "Describe a time you worked effectively in a team." / "Tell me about a team conflict you navigated." | Collaboration, adaptability, empathy, managing disagreement constructively |
| Problem-solving | "Tell me about a complex problem you solved." / "Describe a time you had to analyse data to make a decision." | Analytical rigour, structured thinking, comfort with ambiguity |
| Resilience / Failure | "Tell me about a time things went wrong." / "Describe a setback and how you dealt with it." | Self-awareness, learning orientation, emotional regulation, persistence |
| Communication | "Tell me about a time you persuaded someone who disagreed with you." / "When did you have to explain something complex?" | Clarity, active listening, tailoring message to audience, influence |
| Initiative | "Tell me about a time you went beyond what was expected." / "When did you spot an opportunity others missed?" | Proactivity, ownership, commercial instinct |
| Commercial awareness | "Tell me about a business situation you found interesting recently." / "When did you demonstrate commercial judgement?" | Industry knowledge, business acumen, customer/stakeholder thinking |
| Prioritisation | "Tell me about a time you had too much on and had to manage competing demands." / "When did you have to make a difficult decision about what not to do?" | Time management, judgement, delegation, stress management |
Fully Worked STAR Examples
"Tell me about a time you led a team through a difficult situation."
"Tell me about a time you failed and what you learned from it."
"Tell me about a time you identified a problem customers were having and what you did about it." (Amazon Leadership Principle: Customer Obsession)
STAR vs CAR vs SOAR vs PARADE
| Framework | Structure | Best Used For |
|---|---|---|
| STAR | Situation → Task → Action → Result | Most professional interviews — graduate schemes, consulting, banking, Big 4 |
| CAR | Context → Action → Result | Shorter answers; roles where context is self-explanatory (e.g., senior roles, technical interviews) |
| SOAR | Situation → Obstacle → Action → Result | Questions specifically about challenges, setbacks, or resilience |
| PARADE | Problem → Anticipated consequences → Role → Action → Decision → End result | Senior-level or consulting roles where decision rationale is heavily scrutinised |
For most graduate and early-career interviews, STAR is the right framework. The key is understanding why it works — not mechanically following a formula. Any structured, evidence-based answer that clearly shows what you did and what resulted will score well.
Employer-Specific STAR Frameworks
| Employer | Competency Framework | Interview Style | Guide |
|---|---|---|---|
| Amazon | 14 Leadership Principles — each question maps to a specific LP | STAR expected; preparation requires mapping experiences to LPs explicitly | Amazon Guide → |
| PwC | Commercial awareness, leadership, teamwork, business acumen | STAR behavioural questions + commercial awareness discussion | PwC Interview Questions → |
| Deloitte | Analytical thinking, leadership, communication, innovation | STAR + case study hybrid | Deloitte Interview Questions → |
| Goldman Sachs | Intellectual rigour, resilience, client focus, integrity | STAR + technical markets knowledge | Goldman Sachs Questions → |
| Civil Service | 7 Civil Service Behaviours (Making Effective Decisions, Leadership, etc.) | STAR mapped explicitly to Behaviours — use the Behaviours framework as your prep guide | Civil Service Guide → |
| EY | Fully strengths-based — STAR format is NOT expected at EY | Conversational strengths questions (no STAR structure) | Strengths Interview Guide → |
Common STAR Mistakes to Avoid
- Using "we" instead of "I" in the Action section: Interviewers cannot score what the team did — only what you personally contributed. Replace every "we" in your Action with "I" and a specific action you took. This is the single most common STAR mistake and the easiest to fix.
- Spending too long on Situation: More than 20% of your answer on context is almost always too much. Get into the Action quickly — that's what interviewers are waiting for.
- Vague Actions: "I took ownership of the project" tells the interviewer nothing. What specific steps did you take? "I restructured the project timeline into three phases, moved the highest-risk tasks to week one to surface problems early, and set up daily 15-minute stand-ups to maintain momentum" is specific and scoreable.
- Not quantifying the Result: Results without numbers are weak. "The event was a success" versus "We sold 200 tickets — 40% above our target — and raised £4,800 for the charity." If you genuinely can't quantify, describe the qualitative impact clearly: "The client renewed their contract, which my manager attributed directly to how we handled the relationship during that difficult period."
- Choosing examples without genuine challenge: Interviewers are assessing how you handle difficulty. If your Situation and Task don't involve any real challenge — if success was easy or expected — the competency signal is weak. Choose examples where something was genuinely difficult.
- Recycling the same example for every question: Prepare at least 6 distinct STAR examples before any interview. Using the same story 3 times suggests limited experience and reduces your credibility.
Frequently Asked Questions
Prepare for Every Stage of Your Application
The interview comes after the aptitude test. Practice your numerical reasoning, verbal reasoning, and situational judgement skills with our free timed tests — used by thousands of candidates at the Big 4, banks, and consulting firms.