If a UK interviewer says "tell me about a time when...", they are running a competency interview, and they are usually scoring your answer against a rubric. STAR — Situation, Task, Action, Result — exists so your answer contains the thing the rubric is looking for. Most people know the acronym. Far fewer use it well, and the failures are consistent enough to be worth naming.
What each letter is actually for
Situation — set the scene, fast
One or two sentences. Where you were, when, and what was going on. That is genuinely all. The most common mistake in the whole method is spending a minute here, because context is comfortable to talk about and the rest is not.
Task — what was on you specifically
What were you responsible for? This is a short sentence, and its job is to establish that what follows was yours. "I was asked to get the backlog cleared before the audit in six weeks."
Action — the actual answer
This is 60 to 70 percent of your answer, and the part interviewers are scoring. What did you do, step by step, and why did you choose that? Say "I", not "we" — team credit is generous but it is also how candidates fail competency questions, because the interviewer cannot mark what they cannot attribute to you.
Include the reasoning, not just the steps. "I started with the oldest cases rather than the quickest, because the oldest were the ones generating complaints" tells them how you think, which is the actual point of the exercise.
Result — finish the story
What happened? Quantify it if you honestly can, and if you cannot, say what changed anyway. An answer that trails off without a result is the second most common failure, and it leaves the interviewer with nothing to write down.
Add one line of reflection where it is genuine — what you learned, or what you would do differently. It signals self-awareness, and on many scoring rubrics it is worth explicit marks.
A worked example
Question: "Tell me about a time you had to deal with a difficult stakeholder."
Situation. Last year we were replacing the booking system across four sites, and the site manager at our largest branch was firmly against it.
Task. I was running the rollout, and without that site we would not have hit the switchover date.
Action. Rather than escalating, I went and sat with his team for a morning, because I suspected the objection was not really about the software. It was not — they had been given a system two years earlier that had made their job harder, and nobody had asked them first. So I changed the approach: I got his two most sceptical staff into the configuration sessions, gave them a genuine say in how the booking screens were laid out, and made them the ones who trained their own site. I also agreed a fallback with him in writing, that we would revert if the first fortnight went badly, which cost me nothing and removed the risk he was carrying.
Result. That site went live on schedule and ended up with the lowest error rate of the four. He asked to be involved in the next rollout. What I took from it was that stated objections are often not the real ones, and the fastest route is usually to go and find out rather than to argue.
Notice the proportions: two short sentences of setup, one of task, a long action section with reasoning in it, and a result that actually resolves.
Where people lose marks
- Too much Situation. If ninety seconds have gone and you have not said what you did, you have already lost the answer.
- "We" throughout. The interviewer is marking you, not your team. Use "we" for context and "I" for action.
- No Result. Answers that fade out. Always land it.
- The invented example. Competency interviewers probe. Two follow-up questions is usually enough to expose a story that did not happen, and recovering from that in the room is close to impossible.
- One example stretched over four questions. Prepare five or six.
Preparing without over-scripting
Before an interview, list five or six things you have genuinely done that went well or went badly and taught you something — a project delivered, a conflict handled, a mistake owned, a deadline saved, something improved. Sketch each in STAR shape as bullets, not sentences.
Bullets matter: full scripts come out sounding recited, and the moment an interviewer asks a follow-up your script has no answer. Bullets let you tell the story naturally each time. If you are struggling to think of examples, the exercise in transferable skills is a good way to surface things you have stopped noticing you can do.
The hard part is remembering what you have actually done.
Most people can use STAR once someone explains it. What stalls them is the blank page: which of the hundred things you have done is the right example for this question, for this job? Valiown reads your CV and works through guided questions to build a real picture of your experience, then matches you against live UK roles and prepares you against the ones you are actually pursuing — so the examples you bring are drawn from your genuine history rather than invented on the spot. Free preview on Google Play.
Common questions
What does STAR stand for?
Situation, Task, Action, Result. It is a structure for answering competency questions — the ones that begin "tell me about a time when" — so that your answer contains an actual outcome rather than trailing off.
How long should a STAR answer be?
Around two minutes. The bulk of it should be Action — what you personally did. Situation and Task together should take about twenty seconds; they are context, not the answer.
What if I do not have a good example?
Use a smaller one honestly rather than a big one you have embroidered. Interviewers ask follow-up questions, and invented examples come apart under two of them. A modest, true, well-told example beats an impressive vague one every time.
Can I use the same example for more than one question?
Once, at most, and only if you genuinely draw out a different aspect. Prepare five or six varied examples before an interview and you will rarely be stuck.