STAR Method Interview Answers: A Worked Example
Learn how to structure behavioural interview answers with STAR, see a full worked example, and avoid the most common mistake: too much time on the situation.
By folioV Labs · · 5 min read
"Tell me about a time you disagreed with a colleague." "Describe a project that went wrong." These are behavioural questions, and they are hard to answer well when you are nervous and trying to remember your own career at speed. The STAR method gives you a shape to hang your answer on. It will not make a weak story strong, but it stops a good story from wandering.
What STAR stands for
STAR is four parts, in this order:
- Situation: the context. Where were you, and what was going on?
- Task: your responsibility. What were you specifically expected to do or fix?
- Action: what you did, step by step.
- Result: what happened because of it.
There is a useful fifth part that many guides leave out: a line on what you learned. We will come to that, because it often separates a decent answer from a memorable one.
The interviewer is not testing whether you can recite an acronym. They are listening for evidence of how you behave at work, because past behaviour is the best clue they have about future behaviour. STAR simply makes sure the evidence arrives in a form they can follow.
Why behavioural questions work the way they do
A question like "How do you handle pressure?" invites a vague answer. "Tell me about a time you were under pressure" asks for one real event, which is much harder to bluff and much easier for you to tell well if you have prepared.
Behavioural questions are common across roles and countries, from graduate schemes to senior hires. They tend to cluster around a handful of themes: conflict, failure, leadership, tight deadlines, persuading others, and handling change. You do not need fifty stories. Five or six solid ones, chosen well, can be bent to fit most questions.
A worked example
Here is a full answer to: "Tell me about a time you had to deal with a difficult stakeholder." The candidate is a project coordinator.
Situation. "At my last company, I was coordinating the launch of a new customer portal. Two weeks before go-live, the head of sales asked for a major change to the sign-up flow."
Task. "It was my job to keep the launch on schedule without damaging the relationship, because sales would be the team using the portal every day."
Action. "First, I asked him to walk me through why the change mattered, rather than just saying no. It turned out he was worried about losing leads who abandoned sign-up halfway. I then spoke to our developer and found the full change would take three weeks, but a smaller version, saving partial progress, would take two days. I put both options in front of him with the cost and timing of each, and recommended the smaller one, with the rest scheduled for the following release."
Result. "He agreed to the smaller version. We launched on time, and in the first month the abandoned sign-up rate dropped noticeably, which he mentioned in the next leadership meeting. The larger change went into the next release."
What I learned. "I learned to ask what problem someone is trying to solve before debating their solution. It has saved me a lot of arguments since."
That answer runs to roughly a minute and a half spoken aloud, which is about right.
The most common mistake: too much situation
If you take one thing from this article, take this. Most candidates spend far too long on the Situation.
They explain the company, the team structure, the history of the project, who reported to whom, and what the market looked like that year. Two minutes in, the interviewer still has not heard a single thing the candidate actually did.
The Situation and Task together should take around fifteen to twenty seconds. Two sentences each is plenty. The interviewer needs just enough context to understand your action, nothing more. If a detail does not change how your action makes sense, cut it.
A rough guide to where your time should go:
- Situation and Task: about a fifth of the answer.
- Action: about half. This is the part they are really assessing.
- Result and learning: the remaining third or so.
If you notice yourself still setting the scene after half a minute, wrap it up with "So, the challenge was..." and move on.
Other mistakes worth avoiding
Saying "we" all the way through. Teamwork matters, but the interviewer is hiring you. Make clear what you personally decided and did. "We" is fine for context; use "I" for the action.
Skipping the result. Many answers trail off with "and it all worked out in the end." Be specific. A number is ideal if you have one, but a concrete outcome in plain words works too: a deadline met, a complaint withdrawn, a process adopted by another team. Only quote figures you can stand behind.
Picking a story where nothing was at stake. Choose examples with a genuine problem, a choice you made, and a visible outcome.
Hiding failures. A story where things went wrong is often stronger, provided you are honest about your part and clear about what you changed afterwards. This is exactly where the learning line earns its place.
How to prepare your stories
Sit down with your CV and list six to eight moments you remember clearly: a conflict, a mistake, something you improved, a time you led without being asked, a tight deadline. For each one, write four or five bullet points under the STAR headings. Not a script, just prompts.
Then say them aloud. Reading a story in your head always feels shorter and smoother than it sounds when spoken. Time yourself, and trim the Situation first.
It also helps to tag each story with the themes it could answer. The portal story above works for stakeholder management, but also for prioritisation, compromise and communication. One story, several questions.
The competition for roles is real. folioV's weekly Job Market Pulse tracked 5,920 roles across 562 companies this week, and many of them will have a behavioural round. You can read the latest Job Market Pulse for the wider picture. The point is not to panic about numbers, only to say that a prepared answer is one of the few things in an interview that is fully in your control.
If you would like somewhere to keep your stories and practise them out loud, folioV's Interview Prep & Story Bank lets you rehearse answers with a coach and keep your best stories ready for the next interview.
In short
Keep the Situation brief, spend your time on what you actually did, finish with a clear result, and add one honest line about what you learned. Prepare a handful of real stories, practise them aloud, and you will walk into the room with something much better than a good memory: a plan.