STAR — Situation, Task, Action, Result
Structuring an answer to any behavioural question by showing the logical progression from a context, to a responsibility, to an action, to a measurable impact.
Demonstrating a clear, measurable personal contribution
Why it exists. Before STAR, candidates answered in a disorganised way — too much context, not enough action, zero result. STAR was created to standardise behavioural interviews and assess skills objectively.
What it does. Grounds the answer in real facts, demonstrates a clear personal contribution, quantifies the impact.
In which interviews. All of them. STAR is used by HR, managers, clients, consultancies. It's the absolute base method.
The narrative-coherence bias
STAR exploits the human brain's narrative-coherence bias: a well-built story is perceived as more credible and memorable than a list of abstract skills.
Entry-level version
Tell a story in 4 acts — where, your role, what you did, what it produced.
Senior consultant version
STAR is a tool for demonstrating value. The Action (60% of the time) has to reveal your reasoning, your trade-offs, your stance. The Result has to be multi-dimensional: technical + business + human.
The four steps of the method
- SSituation — the context, dated and bounded in under 3 sentences.
- TTask — your personal role, distinct from the team's role.
- AAction — your decisions, in the first person; about 60% of your speaking time.
- RResult — the impact, quantified (%, €, time, count).
From practical application to an architect's stance
Question: "Tell me about a time you had to fix a critical problem in production."
Situation: in July 2023, senior backend developer at an HR software vendor, hosting a payroll platform for 40 enterprise clients including two CAC40 companies. On a Friday at 4:30 pm, an abnormal load spike: the REST API's response time goes from 120ms to 8 seconds in under an hour.
Task: with the Tech Lead away on leave, appointed by the CTO to lead the crisis response, with a mandate to stabilise the service within 4 hours.
Action: activated CloudWatch Insights to isolate the bottleneck — an unindexed SQL query blowing up after a client's bulk import. Applied a partial index, deployed a Redis caching patch, coordinated two colleagues (client communication, safety rollback).
Result: response time back to 110ms within 2h15, no visible outage for clients, the fix documented in the runbook. A proactive alerting system proposed afterwards then caught 3 similar incidents over the next 6 months before they reached production.
Question: "Describe a major technical transformation project you led."
Situation: between 2021 and 2023, led the migration to GCP of a legacy core-banking system at a regional financial institution, 1.2 million customer accounts. Running on an IBM z/OS mainframe for 17 years with critical COBOL dependencies. Constraints: PCI-DSS level 1, a 99.99% SLA, an internal team with little cloud experience.
Task: architect in charge of the migration strategy and technical governance — target architecture, pattern choices, training 14 in-house developers.
Action: a 6-week diagnostic and a map of 340 candidate microservices (business criticality, technical coupling, ROI). 12-week migration waves, a transitional hybrid architecture with a Pub/Sub event bus, blue/green deployment with a 3-week progressive cutover, twice-weekly war rooms with the CIO.
Result: migration completed in 22 months, 2 months ahead of the original schedule. Infrastructure costs cut by 38% annualised, availability held at 99.97%, a 2023 GCP Partner Award, and 6 Professional Cloud Architect certifications earned by the in-house team.
Freelance variant
As a freelancer, adapt STAR to showcase your autonomy and your ability to operate without a safety net:
Task: stress your autonomy in scoping the engagement itself. "I first audited the real need before proposing an approach."
Result: always add the client-satisfaction dimension. "The client renewed the engagement for 3 more months" or "They recommended me to two of their partners."
Common mistakes
- ✕Starting with "We did..." — the interviewer is assessing YOUR contribution, not the team's.
- ✕Staying vague on results: "it went well", "the client was happy" prove nothing.
- ✕Skipping the Task and going straight from Situation to Action — your personal role is crucial.
- ✕Going past 4 minutes without being asked to elaborate — an effective STAR answer fits in 2-3 minutes.
- ✕Picking an example that's too old (more than 5 years) with no justification.
- ✕Giving no figures — lacking exact numbers, use honest orders of magnitude ("around 30%").
- ✕An Action that's too technical with no explanation of the reasoning — why that choice and not another?
- ✕Ending with no impact — "and the project went well" is not a Result.
Quick checklist
- ✓The Situation is dated and set up in under 3 sentences.
- ✓The Task separates my personal role from the team's role.
- ✓The Action consistently uses "I".
- ✓The Action makes up at least 60% of my speaking time.
- ✓The Result is quantified (%, €, time, count).
- ✓The answer fits between 2 and 3 minutes.
- ✓I can justify every choice if questioned on it.
- ✓The example is less than 5 years old.
Expert advice
Practical exercise
A personal bank of examples
List 8 significant professional situations (success, failure, crisis, innovation). For each one, write a STAR answer of 250 words maximum. Read them aloud and time yourself. The Action should take up 60% of the time.
Video exercise
Record yourself answering 5 behavioural questions. Analyse the Situation / Task / Action / Result ratio and any hesitations.
STAR in one sentence
Situation (context) → Task (your role) → Action (60% — your decisions) → Result (quantified). This is the base method. Master it completely before learning the others.
Want one-to-one support to prepare for your interviews?
An outside perspective to build your bank of examples and rehearse under real conditions.