The STAR method is a four-part structure for answering behavioural interview questions: Situation (the context), Task (what you had to achieve), Action (what you personally did) and Result (what changed because of it). It exists because behavioural interviews ask for evidence, not opinions: 'tell me about a time you...' rather than 'are you a team player?'. STAR turns a rambling anecdote into a short, evidenced story with a measurable ending, which is exactly what a trained interviewer is scoring. It works for graduate schemes, consulting, banking, engineering and public-sector competency panels alike.
Pick a real example that matches the competency being asked about. Spend about 15% of your answer on the Situation, 10% on the Task, 60% on the Action (always 'I', never 'we') and 15% on the Result, quantified wherever you can. Aim for 90 seconds to 2 minutes. Prepare 8-10 stories in advance and reuse them across questions.
What Is the STAR Method?
Behavioural interviewing rests on a simple premise: how you behaved in a comparable situation in the past is better evidence of how you will behave in the future than what you say you would do hypothetically. So interviewers ask for concrete episodes and score them against a competency framework. The STAR method is the candidate-side answer to that: it forces you to supply exactly the four pieces of information the scorer needs, in the order they need them.
Without a structure, most candidates over-explain the background, never make clear what they personally did, and finish with a vague 'and it went well'. That answer can score zero against a competency even when the underlying story is excellent. The structure is not decoration. It is the difference between an interviewer being able to tick a scoring behaviour and having to guess.
The Four Components and Your Time Budget
- Situation (about 15%, roughly 15-20 seconds): where, when, and what was at stake. Two or three sentences. The interviewer needs enough context to judge difficulty, and nothing more.
- Task (about 10%, roughly 10-15 seconds): your specific responsibility. This is the sentence that separates you from the team. 'I owned the migration plan for three of the eight systems.'
- Action (about 60%, roughly 60-75 seconds): what you did, step by step, and (critically) why you chose to do it that way. Use 'I' throughout. Include the decision you made when it was not obvious, because that is where the competency lives.
- Result (about 15%, roughly 15-20 seconds): what changed. Quantify it: percentage, money, time saved, error rate, retention, headcount. Close with one sentence on what you learned or what you did differently afterwards.
If your Action is not the longest part of your answer, you are telling a story instead of giving evidence. Most weak answers spend half of their airtime on the Situation. Interviewers score the Action.
STAR vs CAR, SOAR and STARL
Different employers and coaches use different acronyms, but they are variations on the same structure. If a recruiter tells you to use CAR or SOAR, you do not need to relearn anything. You are being asked to compress or extend the same four elements.
| Formula | Expression |
|---|---|
| STAR | Situation - Task - Action - Result |
| STARL / STARR | STAR + Learning (or Reflection) at the end |
| CAR | Context - Action - Result (Situation and Task merged) |
| SOAR | Situation - Obstacle - Action - Result |
| PAR | Problem - Action - Result |
| CARL | Context - Action - Result - Learning |
Practical advice: prepare in STAR, and add a one-sentence learning at the end. That single sentence converts a STAR answer into STARL, satisfies employers who explicitly score reflection, and costs you five seconds.
The 12 Most Common Behavioural Questions
- 1Tell me about a time you dealt with a difficult colleague or stakeholder.
- 2Describe a situation where you had to meet a very tight deadline.
- 3Give me an example of when you showed leadership without a formal title.
- 4Tell me about a time you failed, and what you did next.
- 5Describe a time you had to influence someone who did not report to you.
- 6Give an example of adapting to a significant, unexpected change.
- 7Tell me about a time you went beyond what was asked of you.
- 8Describe a decision you made with incomplete information.
- 9Give an example of how you handled conflict inside a team.
- 10Tell me about a time you had to learn something complex, quickly.
- 11Describe a time you spotted a problem nobody else had noticed.
- 12Tell me about a time you received difficult feedback.
Twelve questions, but only about six underlying competencies: leadership, teamwork and conflict, resilience and failure, problem solving and judgement, influence and communication, and initiative. Prepare for the competencies, not for the question wordings.
Rehearse STAR answers out loud and get feedback on structure, specificity and whether your Action actually carries the answer. The free preview includes 5 AI coach messages.
Start behavioural interview trainingWorked STAR Examples
Four fully worked answers. Notice how short the Situation is in each, how the Action names specific decisions, and how every Result carries a number.
I was a project manager at a marketing agency. Two weeks before launch, our largest client told us the campaign was off-brand and threatened to pull it.
I owned the client relationship and the delivery timeline. I had to find out what was actually wrong, fix it, and still launch on the agreed date.
I called them within the hour and spent the first fifteen minutes only listening and taking notes. That surfaced the real issue: it was brand consistency in the visuals, not the creative concept, which is what my team had assumed. I turned their feedback into three specific, scoped changes rather than a general redesign, checked with my designers that all three fit inside the remaining schedule, and sent the client a one-page summary of what we would change and what we deliberately would not. I then set up a ten-minute daily check-in for the final two weeks so no surprise could build up again.
The campaign launched on the original date. The client moved their post-project satisfaction rating from 5 to 9 out of 10 and renewed for another year. I now open every client escalation by separating what they said from what they meant before I brief my team.
During an internship at a financial services firm, the senior analyst leading a major client presentation was signed off sick the day before it.
I was asked to complete the analysis and build the deck in under 24 hours, work that had been scoped for three days.
Instead of trying to do everything faster, I cut scope. I asked the client relationship manager which three questions the client actually cared about, and dropped every section that did not answer one of them. I reused an existing model rather than rebuilding one, so my time went into checking inputs rather than structure. I had a draft with the relationship manager by midnight, and used the two hours before the meeting to rehearse the three slides I would be asked about.
The presentation ran on schedule, the client commissioned a follow-on piece of work, and my manager cited the prioritisation call (not the hours) in my end-of-internship review. The lesson I took was that under a hard deadline the leverage is in scope, not speed.
In my first year as an analyst I owned a monthly reporting pack that went to the regional leadership team.
I had to deliver it accurately on the second working day of every month.
In March I shipped it with a broken currency conversion: one region was reported in local currency instead of euros, which overstated its revenue. I found the error myself the next morning while preparing a follow-up. I told my manager immediately rather than quietly correcting it, sent a short correction note to every recipient with the corrected figure and the cause, and then built a validation check into the model that flags any region whose month-on-month change exceeds 25%. I also added a second-pair-of-eyes step before send-out.
No decision had been taken on the wrong number, because the correction went out within eighteen hours. The validation check caught two genuine data-feed errors in the following six months. It also changed how I work: I now build the error check before I build the report.
As a junior engineer I found that our release process required three manual steps that were causing roughly one failed deployment a week.
I wanted the team to automate them, but I did not own the pipeline and the two senior engineers who did were fully committed to a customer project.
Rather than argue for it in the abstract, I spent two evenings measuring the cost: I logged every failed deployment for a month and converted it into engineer-hours lost. I then built a working prototype of the automation for the single least risky step and demonstrated it in a ten-minute slot at our team meeting. I asked for something small and specific, a review of my prototype, not a commitment to the whole idea.
The prototype was merged the same week. The other two steps followed within a month because the pattern was already proven, and failed deployments dropped to roughly one a month. What worked was arriving with evidence and a small ask, not with an opinion and a big one.
Building a 10-Story Story Bank
You cannot prepare an answer for every possible question, and you do not need to. Almost every behavioural question maps onto one of a small number of competencies, and a good story usually covers two or three of them. Build a bank of eight to ten stories and you can answer almost any question by choosing which angle of a story to foreground.
- 1Leadership: a time you took responsibility for an outcome that involved other people.
- 2Teamwork and conflict: a disagreement you resolved without escalating it.
- 3Resilience and failure: something that went wrong that you owned and fixed.
- 4Problem solving: a messy problem you structured before you solved.
- 5Influence: persuading someone with no obligation to listen to you.
- 6Initiative: something you started that nobody asked you to start.
- 7Working under pressure: a hard deadline or a resource constraint.
- 8Adaptability: a change of direction you absorbed and made work.
- 9Analytical thinking: a decision you drove with data rather than instinct.
- 10Customer or stakeholder focus: an example of putting the end user first, with a trade-off you had to accept.
The stakeholder example above answers 'difficult stakeholder', 'influencing without authority' and 'working under pressure'. You simply change which decision you put at the centre of the Action. Prepare stories, then practise re-angling them.
Where You Will Meet Behavioural Questions
Behavioural questions are no longer confined to the final round. They show up in recorded video screens, in structured phone screens and in assessment centre interviews, and the format changes how you should deliver the same answer.
| Publisher | Questions | Time | Difficulty | Notes |
|---|---|---|---|---|
| HireVue (one-way video) | Typically a handful of set questions | 1-3 minutes per answer, often with a short prep window | N/A | No interviewer to read. Keep the Situation very short and get to the Action fast; you cannot be prompted. |
| Live video interview (Teams, Zoom) | 4-8 behavioural questions | 45-60 minutes total | N/A | You can be probed. Expect follow-ups such as 'what would you do differently?' |
| Structured competency panel | One question per competency | Roughly 5-8 minutes per competency | N/A | Scored against a framework. Assessors are ticking behaviours, so signpost your STAR sections out loud. |
| Assessment centre interview | Mixed with exercises | 30-60 minutes | N/A | Often uses examples from the day itself; be ready to STAR the group exercise you just did. |
| Final / partner interview | Fewer, deeper questions | 30-45 minutes | N/A | Expect the interviewer to dig into a single Action for several minutes. Depth beats breadth. |
How Interviewers Actually Score You
- Against a framework, not against other candidates in the room. Each competency has defined positive and negative indicators, and the interviewer notes evidence against them while you speak.
- Evidence, not adjectives. 'I am very organised' scores nothing. 'I built a shared tracker and cut duplicate work by two days a sprint' scores.
- Specificity over scale. A small example described precisely beats a huge project described vaguely. Assessors know when you are hiding behind the size of the project.
- Ownership. Every 'we' is a data point the interviewer cannot attribute to you. This is the most common reason strong candidates score in the middle band.
- Follow-up resilience. Expect probing: why that decision, what was the alternative, what would you change. A memorised answer collapses here; a real one does not.
Nine Mistakes That Sink Good Answers
- Saying 'we' instead of 'I'. The single most costly habit in behavioural interviews.
- A Situation that runs for a minute. Cut it to two sentences.
- No number in the Result. If nothing was measured, say what changed instead: a decision, a process, a retained client.
- Choosing a story that does not match the competency. A teamwork story does not answer a leadership question, however good it is.
- Word-for-word memorisation. It sounds rehearsed and it falls apart under a follow-up question.
- Hiding the failure in a 'failure' question. Interviewers are scoring ownership and correction, not the absence of failure.
- Describing intentions instead of actions. 'I wanted to align the team' is not an action; 'I ran a 30-minute session to agree the three priorities' is.
- Running past two minutes. Long answers are read as poor prioritisation.
- Ignoring the employer's own framework. Most large employers publish their competencies or values. Map your stories onto them before the interview. The situational judgement stage of the same process is usually built on exactly the same framework.
A 7-Day STAR Preparation Plan
- 1Day 1: Mine your experience. List every project, crisis, deadline and disagreement from the last three years. Aim for 20 raw candidates, unpolished.
- 2Day 2: Map to competencies. Take the employer's published competencies or values and assign your best raw story to each. Gaps tell you what to dig for.
- 3Day 3: Write ten stories in STAR. Bullet points only, never full scripts. One page per story, with the Action getting most of the page.
- 4Day 4: Add the numbers. Go and find the actual figures: percentages, hours, euros, error rates, headcount, satisfaction scores. This is the step almost everyone skips and it is the one that changes scores.
- 5Day 5: Say them out loud, timed. Record yourself. Anything over two minutes gets cut. Anything where you say 'we' gets rewritten.
- 6Day 6: Practise the probes. For each story, answer: why did you choose that? What was the alternative? What would you do differently? What did others think?
- 7Day 7: Re-angle. Take three stories and answer three different questions with each. This is what makes you flexible on the day rather than brittle.
MakingMoves.ai covers 50+ test categories and 113,000+ practice questions, and the AI interview coach lets you rehearse behavioural answers with feedback on structure and impact. Free preview: 4 questions per test and 5 AI coach messages. Plans: GROW EUR 19,95 per week, PRO EUR 49,95 per month, MAX EUR 79,95 per month.
Browse interview questionsFrequently Asked Questions
Between 90 seconds and two minutes for most questions. Shorter than 60 seconds usually means the Action is missing detail; longer than two minutes usually means the Situation has taken over.
Once is fine if you foreground a different decision the second time, but avoid it if you can, interviewers are looking for breadth of evidence. This is exactly why you build a bank of eight to ten stories rather than perfecting three.
Use university projects, part-time jobs, sport, volunteering or societies. Graduate assessors expect this and score the behaviour, not the setting. A student society budget crisis can evidence the same competency as a corporate one.
In a structured competency panel, light signposting helps the assessor find the evidence: 'the situation was...', 'so what I did was...'. In a conversational interview, keep the structure but drop the labels.
Yes, provided the Result explains what you learned and what you changed. Failure questions score ownership and correction. A story where the outcome was rescued by someone else, and you take credit for it, is the one that damages you.
It works better there than anywhere, because nobody will prompt you back on track. Cut the Situation to one sentence, start the Action within about twenty seconds, and finish with a quantified Result before the timer ends.
Most employers pair the behavioural interview with online tests. Practise the aptitude side of the same process for free, 4 questions per test, no payment details required.
Try the free testsIngmar van Maurik is the founder of MakingMoves.ai and Assessment-Training.com. With 10+ years in psychometric assessment design, he has helped over 1 million professionals prepare for job assessments.