Competency-based questions — the “tell me about a time when...” ones — reward candidates who've prepared a structure in advance, not just candidates with good stories. The STAR method is that structure, and it's worth building out properly before you walk into the room.
The people who ramble in competency interviews usually have perfectly good examples in their head — they just haven't organised them. Ask someone to describe a time they handled a difficult client without warning, and even a genuinely strong candidate can end up circling the point, backtracking to add context they forgot, and running out of time before reaching what they actually did. STAR fixes that by giving you a shape to follow under pressure.
The four parts, and what each one is actually for
- Situation. Set the scene in two or three sentences — where you worked, what the context was, why it mattered. Resist the urge to over-explain; the interviewer needs just enough to understand what follows.
- Task. What specifically were you responsible for, or what needed to happen? This is often skipped or blended into the Situation, but keeping it distinct helps the interviewer see exactly what you were being judged against.
- Action. The part that actually matters most. What did you personally do — not your team, not your manager, you? Use “I” rather than “we” wherever the action was genuinely yours. This is where interviewers are scoring the competency itself.
- Result. What happened as a consequence. Numbers help if you have them — time saved, complaints resolved, targets hit — but an honest qualitative outcome works too. If you learned something from a result that wasn't perfect, say so; it often lands better than a suspiciously tidy success story.
Build your examples before the interview, not during it
The single biggest improvement most candidates can make is preparing five or six strong examples in advance, each mapped loosely to a common competency — teamwork, conflict, leadership, problem-solving, handling pressure, making a mistake. You won't know the exact wording of the question beforehand, but a well-chosen example can usually flex to answer two or three different competencies depending on which part you emphasise.
Write each one out as bullet points under S, T, A, R — not full paragraphs. The goal is to know the shape of the story cold, not to recite it word for word. Reciting a memorised script tends to sound stilted and falls apart the moment the interviewer asks a follow-up question you hadn't scripted for.
Common competencies worth having examples ready for
- A time you dealt with a conflict or disagreement at work
- A time you missed a deadline or made a mistake, and what you did next
- A time you had to influence someone without formal authority over them
- A time you managed several competing priorities at once
- A time you took the lead on something without being asked
Watch the Action section
It's easy to spend most of your answer on the Situation because it's the easiest part to talk about. Consciously push yourself to spend the most time on Action — that's the bit the interviewer is actually scoring, and it's the bit most candidates underweight without realising.
These questions often come up alongside more general ones too — worth reading our rundown of common UK interview questions so you're not caught off guard switching between styles. And if you make it through to a second round, the questions usually get more specific and more senior — see our guide to preparing for a second interview.
Frequently asked questions
What does STAR stand for?
Situation, Task, Action, Result. It's a structure for answering competency-based questions: set the scene, explain what you needed to achieve, describe what you specifically did, and finish with the outcome.
How long should a STAR answer take to deliver?
Roughly two to three minutes is the sweet spot. Under a minute usually means you've skipped detail the interviewer needed; over four or five minutes and you risk losing them in the Situation before you've even reached the Result.
What if my example doesn't have an impressive result?
Not every story needs a dramatic outcome. A steady, honest result — you resolved the issue, the client stayed, the deadline was hit — is perfectly fine. What interviewers are really scoring is the Action section: what you specifically did and how you approached the problem.
Can I reuse the same example for different questions?
Sometimes, if it genuinely fits — a strong example often demonstrates more than one competency. But don't force it. If you're stretching a story to fit a question it doesn't really answer, it usually shows.
Let's prepare your examples together
Talk to us about your interview coming up — we'll help you build STAR answers that actually hold up under follow-up questions.
Get Started