Most people are bad at talking about their own work. Not because they haven’t done good work, but because they’ve never been taught how to describe it. You know you handled a tricky project well. You just struggle to explain what “well” actually looked like.
This is where the STAR method comes in. It’s a simple structure that helps you turn a vague achievement into a clear, convincing story, whether you’re writing a CV bullet point or answering a question in an interview.
What is the STAR method?
STAR stands for four parts of a story:
- Situation: the context. One sentence is enough.
- Task: what you were responsible for.
- Action: what you actually did.
- Result: what happened, backed by something concrete.
The order is important, as is the balance. Situation and Task should be short. Action is where the detail lives and it should make up around 60% of your answer. Result provides the evidence of your success.
Why recruiters and interviewers like it
A recruiter reading your CV wants evidence, not a job description. “Responsible for managing client accounts” tells them what your role was. It doesn’t tell them what you did with it. STAR forces you to demonstrate your own contribution rather than just list your duties.
It works the same way in an interview. Without structure, answers tend to sound vague, and the interviewer is left guessing what you actually did versus what your team did. STAR keeps the focus on you, and it gives the interviewer something specific to remember once the interview is over.
Using STAR on your CV
CV bullet points don’t have room for four separate sentences, so Situation and Task usually get compressed into a short opening clause. That leaves more space for Action and Result, which is where the real value sits.
Here’s the difference in practice:
Before: Responsible for improving customer response times.
After: Redesigned the customer support queue during a busy period, cutting average response time from six hours to under two.
The second version still fits on one line. But it shows what you did and what changed because of it.
Using STAR in an interview
Spoken answers give you more room, so pacing becomes important. Get through Situation and Task quickly, then slow down for Action.
A few things help here:
- Talk through the decisions you made, not just the outcome.
- Use “I” rather than “we” when describing your own contribution. You can mention the team, but be clear about your part.
- Keep going until you reach a Result, even if the story feels finished before that. An answer without a result feels unresolved.
If the outcome wasn’t a clear success, that’s fine. You can still close with what you learned or what changed as a result. Interviewers are often more interested in how you handled a setback than in a perfect win.
Common mistakes people make with STAR
A few patterns come up again and again:
- Spending too long setting the scene and running out of time for Action.
- Giving a result with no number, comparison or outcome attached, so it doesn’t actually demonstrate your achievement.
- Describing what the team achieved rather than what you personally did.
Each of these waters down an otherwise good story, so it’s worth checking your answers against this list before an interview.
Two worked examples
Example one: Turning around a sales slump
Situation: Sales fell for two straight quarters after a competitor entered the market.
Task: As sales manager, I needed to rebuild the pipeline within one quarter.
Action: I reviewed every lost deal from the previous six months and found that pricing was the main objection. I restructured our three service tiers to close that gap, then retrained the team on the new pitch over two weeks.
Result: Sales grew by 22% the following quarter, above where they’d been before the drop.
Example two: Fixing a slow month end process
Situation: The finance team spent three days each month closing the books, and errors kept slipping through.
Task: I was asked to fix the process without adding headcount.
Action: I mapped every step in the close, removed duplicate approvals, built a checklist for the team to follow, and moved two manual reports into a shared template.
Result: Month end close dropped from three days to one, with no errors reported over the following six months.
Both examples follow the same pattern: a short setup, most of the detail in the Action, and a Result with a real number attached. That’s what makes them convincing.
How to practise it before an interview
You don’t need to prepare for every possible question. Instead, pick three or four stories from your own experience that show different strengths, such as problem solving, leadership or working under pressure.
Write each one out in full STAR form beforehand. Then read it aloud and check the Action section is doing most of the work. If it isn’t, that’s usually where the fix is needed.
Final thought
STAR isn’t a trick or a formula to game an interview. It’s simply a way to make sure the work you’ve already done gets noticed. Once you get used to thinking in this shape, it becomes easier to spot your own achievements and put them into words, on paper and in person.
If you’d like help turning your own experience into CV bullet points or interview stories that follow this structure, get in touch and we can work through it together.