Why Competency Questions Catch So Many People Out

You have a strong CV, you meet the person specification, and you have walked into the interview feeling reasonably confident. Then comes the question: "Tell me about a time you dealt with a difficult stakeholder." Suddenly your mind goes blank, and you find yourself rambling about a project that finished two years ago without ever quite explaining what you did or why it mattered.

This is the most common interview stumbling block in the UK, and it is rarely about a lack of experience. Most candidates have plenty of good examples. The problem is structure. Interviewers assessing competencies are not really listening for the best story — they are listening for evidence, and evidence is much easier to hear when it arrives in a predictable order. That is exactly what the STAR method gives you.

What STAR Actually Means

STAR is a simple acronym that breaks an answer into four parts:

• Situation — the context. Where were you, what was happening, and what was at stake?
• Task — your specific responsibility. What were you asked to do, or what did you decide needed doing?
• Action — what you actually did, step by step. This is the heart of your answer.
• Result — the outcome, ideally with something measurable attached.

The magic is not in the acronym itself but in the discipline it enforces. Instead of a meandering anecdote, you deliver a compact piece of evidence that an interviewer can tick off against their scoring sheet while you are still speaking.

Build Your Evidence Bank Before the Interview

Almost nobody can construct a polished STAR answer on the spot, so do the work beforehand. Take the job description and highlight every competency it mentions — things like "managing competing priorities", "influencing without authority", "delivering under pressure", or "working with external partners". Then, on a single sheet of paper, list eight to ten occasions when you genuinely demonstrated those behaviours.

Spread them widely. Include something from your current or most recent role, something from earlier in your career, and something from outside paid employment if it is relevant — a volunteering role, a committee position, or a difficult situation you resolved in a part-time job while studying. A common mistake is relying on the same two examples for every question, which quickly starts to sound thin.

For each example, jot down the four STAR elements in note form. You do not need a script. You need a hook — a single phrase like "the supplier crisis in March" — that lets you retrieve the whole story under pressure.

Make the Action Section Earn Its Place

If there is one part of STAR that candidates rush, it is the Action. They spend ninety seconds on the Situation and then say, "so I sorted it out". Interviewers cannot score that.

Use "I" rather than "we" wherever it is honest. Describe the thinking as well as the doing: what options you considered, why you chose the approach you did, who you spoke to, and how you kept people informed. If you delegated, say so and explain why that person was the right choice. If you had to push back on a senior colleague, say that too — most competency frameworks reward evidence of judgement, not just activity.

Keep the Situation brief. Two or three sentences is usually enough to set the scene before you move on. The balance most interviewers find persuasive is roughly ten per cent Situation, ten per cent Task, sixty per cent Action, and twenty per cent Result.

Bring the Result to Life with Numbers

A vague ending drains the energy from an otherwise excellent answer. "It went well in the end" tells the interviewer nothing. Wherever you can, attach a figure, a timescale, or a concrete consequence.

• Time saved: "It cut our monthly reporting process from three days to about four hours."
• Money: "We recovered around £18,000 in unbilled work."
• Relationships: "The client renewed for a further two years and specifically mentioned the turnaround."
• Learning: "I now build a written escalation route into every project at the outset."

That last type matters more than people realise. Not every story ends in triumph, and a well-told example of something that went wrong, what you learned, and how you changed your approach can be far more compelling than a polished success. Just make sure you land on the learning rather than the failure.

Common Mistakes That Weaken a Good Story

Watch out for a few recurring habits. Rambling past the two-minute mark is the most frequent — aim for around ninety seconds to two minutes per answer and then stop talking. Over-preparing a word-for-word script is another; it sounds rehearsed and collapses the moment you are asked a follow-up question. So is ignoring the question you were actually asked because you were desperate to use a particular example.

Finally, avoid describing a team achievement as though you did it alone. Interviewers have heard enough of those, and they tend to ask, "and what was your specific contribution?" — which is an uncomfortable moment if you have not prepared for it.

Practise Out Loud, Then Trust Yourself

Reading your notes silently is not practice. Say your answers aloud, ideally to someone who will interrupt with follow-up questions, because that is what a real interview feels like. Record yourself once and listen back — you will instantly hear where the waffle lives and where the Result needs sharpening.

After a few rounds, the structure becomes automatic. You will not need to think about Situation, Task, Action and Result in the room; you will simply find that the story arrives in the right order, with the evidence in the right place. That quiet competence is exactly what the interviewer is hoping to see.