The STAR method: how to answer behavioural interview questions, with examples
STAR stands for Situation, Task, Action and Result. Here is how to use it to answer "tell me about a time" questions in under two minutes, with three worked examples and the mistakes that cost candidates offers.
Key takeaways
- STAR stands for Situation, Task, Action and Result. Use it for behavioural questions that start "Tell me about a time" or "Give an example of".
- Spend most of your answer on the Action: what you did, step by step, in the first person.
- Finish with a Result you can measure, and say what you learned if it didn't go to plan.
- Aim for 90 seconds to two minutes per answer, which is roughly 250 to 300 spoken words.
- Prepare six to eight stories before the interview. Most behavioural questions can be answered with one of them.
On this page
The STAR method is a simple structure for answering behavioural interview questions: describe the Situation, your Task, the Action you took and the Result. It keeps answers focused, gives the interviewer the evidence they are scoring, and stops you rambling when you are nervous.
Behavioural questions come up in almost every interview, from graduate schemes to senior leadership roles. This guide shows how to build a STAR answer, with three worked examples and a way to prepare that covers most questions you will be asked.
What the STAR method is
Each letter is one part of your answer. The proportions are a rule of thumb, but they matter: most weak answers spend too long on the situation and too little on the action.
| Part | What it covers | Share of your answer | Sounds like |
|---|---|---|---|
| Situation | The context, in one or two sentences | About 15% | "Last year our team was three weeks from a product launch when..." |
| Task | What you were responsible for, or the goal | About 10% | "I was asked to get the launch back on track without moving the date." |
| Action | What you did, step by step | About 55% | "First I... Then I... When that didn't work, I..." |
| Result | The outcome, with numbers if you can, and what you learned | About 20% | "We launched on time and cut support tickets by 30%." |
When to use STAR
Use STAR for any question that asks about something you have done. These are called behavioural or competency questions, and they usually start with:
- "Tell me about a time when..."
- "Give me an example of..."
- "Describe a situation where..."
- "Have you ever..."
Interviewers ask them because past behaviour is a reasonable guide to future behaviour. Many employers score your answer against set criteria, such as communication or problem solving, so a clear structure makes it easier for them to give you credit.
How to build a STAR answer
- Pick the right story. Choose an example where you personally made a difference, ideally from the last two or three years. It should match the skill the question is testing.
- Set the scene quickly. One or two sentences: where you were, what was happening and why it mattered. Leave out names and background the interviewer doesn't need.
- Make your task clear. Say what you owned. If it was a team effort, explain your part of it.
- Walk through your actions. Use "I", not "we". Give two to four specific steps and explain why you chose them. This is where the interviewer learns how you think.
- Land the result. Give a number if you can: time saved, revenue, satisfaction scores, error rates, people trained. Then add one sentence on what you learned.
- Stop. Finish on the result and let the interviewer ask a follow-up. Trailing off with "so yeah, that's it" weakens a good answer.
STAR answer examples
The examples below are illustrative, written to show the structure. Use them as a pattern for your own experience, not as scripts.
"Tell me about a time you dealt with conflict"
| Part | Answer |
|---|---|
| Situation | Two months into a website rebuild, the design lead and the engineering lead disagreed about scope. Design wanted a full redesign of checkout; engineering said it would add six weeks. |
| Task | As project manager, I had to agree a scope both teams would commit to without moving our launch date. |
| Action | I met each lead separately to understand what they were protecting. Design was worried about conversion; engineering was worried about payment risk. I pulled our checkout data, which showed most drop-off happened on one step. I proposed redesigning that step for launch and the rest in the next phase, and wrote up the trade-off for our sponsor so the decision was on record. |
| Result | Both leads signed off within a week. We launched on time, checkout conversion rose 12% in the first month, and the phase-two work started on schedule. I now separate the people from the problem early, before positions harden. |
Why it works: the conflict is about work, not personalities, the candidate uses data to move the conversation forward, and the result has a number and a lesson.
"Tell me about a time you failed"
| Part | Answer |
|---|---|
| Situation | In my first year in sales, I lost what would have been our largest deal of the quarter in the final week. |
| Task | I was the account executive responsible for the deal from first call to contract. |
| Action | Looking back, I had only ever spoken to one person at the customer, who loved the product but didn't control the budget. When finance got involved at the end, they had no context and chose a cheaper option. Afterwards I asked my manager to review the deal with me, and I built a simple checklist: name the budget holder by the second meeting and get them on a call before sending a proposal. |
| Result | We didn't win that deal back. But over the next two quarters my win rate on deals over $50k went from 18% to 31%, and my manager asked me to share the checklist with the team. |
Why it works: it is a real failure with a clear cause the candidate owns, and the result shows a lasting change rather than a happy ending.
"Give an example of when you led without authority"
| Part | Answer |
|---|---|
| Situation | On my ward, handovers between shifts regularly overran by 20 minutes, and important details were sometimes missed. |
| Task | I wasn't a manager, but I wanted to fix it and asked the ward manager if I could trial a new approach. |
| Action | I asked colleagues on each shift what slowed handovers down. The common answer was that everyone used a different format. I drafted a one-page structured template, tested it with two colleagues for a week and adjusted it with their feedback. I then ran three short sessions so everyone on the ward had seen it before we switched. |
| Result | Handovers dropped to around ten minutes, and the number of follow-up calls about missed information fell noticeably in the first month. The template was adopted by a neighbouring ward. |
Why it works: the candidate shows influence through listening, testing and bringing people along, which is what this question is really about.
Common STAR mistakes
- Too much situation. If you are still setting the scene after 30 seconds, cut it. The interviewer is waiting for what you did.
- "We" instead of "I". Interviewers can't hire your team. Describe your own actions, while giving credit to others where it is due.
- No result. Ending on the action leaves the interviewer guessing. Always say what happened.
- Vague results. "It went really well" is weak. "We cut onboarding from two weeks to four days" is memorable.
- The wrong story. A great story that answers a different question still scores poorly. Listen for the skill being tested.
- Memorised scripts. Know your stories, not your sentences. Answers recited word for word sound rehearsed and fall apart under follow-up questions.
STAR, CAR, SOAR and PAR
You may see other names for the same idea. They are all ways to show what you did and what happened.
| Method | Stands for | Best for |
|---|---|---|
| STAR | Situation, Task, Action, Result | Most behavioural questions |
| CAR | Challenge, Action, Result | Shorter answers, or when the task is obvious |
| SOAR | Situation, Obstacle, Action, Result | Questions about overcoming difficulty |
| PAR | Problem, Action, Result | Quick examples on CVs and in cover letters |
Pick one and use it consistently. STAR is the most widely known, and interviewers trained in competency interviewing will recognise it.
Build a story bank before the interview
You don't need a different story for every possible question. Six to eight strong stories, each showing more than one skill, will cover most behavioural interviews.
| Story to prepare | Questions it answers |
|---|---|
| Your proudest achievement | Biggest success, impact, motivation |
| A problem you solved | Problem solving, initiative, analytical thinking |
| A disagreement you resolved | Conflict, teamwork, communication |
| A mistake or failure | Failure, learning, resilience |
| A time you led others | Leadership, influence, ownership |
| A tight deadline | Pressure, prioritisation, organisation |
| A difficult customer or stakeholder | Stakeholder management, empathy, persuasion |
| A change you made happen | Adaptability, innovation, leading change |
For each story, write one line per STAR letter, note the numbers, and practise saying it out loud. Time yourself: 90 seconds to two minutes is the target.
Frequently asked questions
What does STAR stand for?
Situation, Task, Action and Result. You set the scene, explain what you were responsible for, describe what you did and finish with the outcome.
How long should a STAR answer be?
Around 90 seconds to two minutes, or about 250 to 300 spoken words. If the interviewer wants more detail, they will ask a follow-up question.
Can I use the same story for more than one question?
Yes. A strong story often shows several skills, such as leadership and problem solving. Just avoid using the same story twice with the same interviewer, and lead with the part that answers the question.
What if my result wasn't a success?
Say so, then explain what you learned and what you did differently next time. Interviewers asking about failure want to see honesty and reflection, not a disguised success story.
Should I use STAR for every interview question?
No. Use it for behavioural and competency questions about past experience. Technical questions, case interviews and questions such as "Why do you want this job?" need a different structure.