This guide is about applying for jobs in the UK.

You can prepare for most of an interview, and competency interview questions are the part you can prepare for best of all. They almost always open the same way: "give me an example of a time when". That predictable shape is a gift, because it tells you exactly what the interviewer wants before they finish the sentence. They want a story with a beginning, a middle and an end, and they want you in the middle of it.

The problem is rarely a lack of examples. It is structure. Under mild pressure, a good story comes out as a vague summary that never reaches the point. The STAR method fixes that, and it is the most reliable structure for competency based interview questions and answers in any UK interview. If you want the wider picture first, our guide to interview questions and answers covers the full range of what to expect; this guide goes deep on the behavioural ones.

What competency interview questions are

A competency question asks you to evidence a behaviour with a real past example, on the principle that what you did before predicts what you will do next. They are standard on graduate schemes and across the UK public sector, and common everywhere else.

How to spot a competency question when it lands

Competency questions are easy to recognise once you know the openings. They ask for a specific past event rather than an opinion or a hypothetical. Listen for these stems:

"Give me an example of a time when you..."
"Tell me about a situation where you had to..."
"Describe an occasion when you..."
"Walk me through how you handled..."

The competency itself is usually hidden in the job description. A role that lists "works well under pressure" and "manages competing priorities" is telling you which competency questions are coming. Read the description, underline every behaviour it names, and you have your interview question list before anyone asks it.

Which competencies the questions are really probing

Behind the phrasing, most competency interview questions test one of a small set of behaviours: teamwork, problem solving, leadership, resilience under pressure, handling conflict, adaptability, and taking ownership of a failure. The interviewer is not interested in the project for its own sake. They are listening for what you did inside it, and whether the result holds up.

That is the trap in the format. A genuinely impressive project can produce a weak answer if you narrate the project and forget yourself. The competency lives in your actions, so the structure you use has to push those actions to the front. That is precisely what the STAR technique does.

The STAR method, step by step

STAR stands for Situation, Task, Action, Result. It is the standard interview STAR technique because it forces every answer to a measurable end rather than letting it drift. Build each answer in four moves:

Situation. One or two sentences of context. Where you were, what was happening. Resist the urge to over-explain here, because the setup is the least scored part.
Task. What you specifically were responsible for. This is where you separate yourself from the team, so use "I", not "we".
Action. The heart of the answer. What you actually did, step by step, and why. Spend most of your time here, because this is the competency in motion.
Result. What changed because of your actions. Make it concrete: a deadline met, a cost saved, a measurable improvement, a lesson applied since.

One discipline carries the whole job interview STAR technique: the action and the result are the answer, so the situation and task should be short. If you find an answer running long, the setup is almost always the culprit.

Without STAR versus with STAR

The difference is easiest to feel side by side. Both answers below respond to the same competency question, "tell me about a time you handled a difficult stakeholder".

Without STAR

"There was a client who was quite hard to deal with and kept changing what they wanted. It was frustrating for everyone, but we managed to keep them happy in the end and the work got delivered. I think I am good at staying calm with difficult people."

The interviewer cannot score this. There is no specific action, no measurable result, and the closing line is a claim rather than evidence.

With STAR

"A client kept reopening agreed designs late in the project, which threatened our launch date (situation). I owned the relationship and the timeline (task). I set up a weekly fifteen-minute review so changes were caught early, and I wrote a one-page change log that showed the cost of each late request in days (action). The client stopped reopening signed-off work, and we launched on the original date (result)."

Same story, but now every part the interviewer scores is visible: your action and a result they can believe.

Notice that the situation in the strong version is a single clause. Everything earns its place, and the answer still lands inside two minutes.

Two worked competency answers

Here are two more competency based interview questions and answers, built the same way. Read them for the shape, then rebuild each one from your own experience rather than borrowing the words, because an interviewer can hear a borrowed story.

Teamwork: a time you worked in a team

"Give me an example of a time you contributed to a team's success."

What good looks like:

A clear role for you inside the team, not a blur of "we"
One specific thing you did that the team needed
A shared result, with your contribution still visible

Model answer: "On a six-person project to migrate our reporting to a new tool, the team kept duplicating work because no one owned the task list (situation). I volunteered to coordinate it (task). I built a shared board, ran a five-minute stand-up each morning, and flagged blockers to our manager the same day rather than waiting for the weekly meeting (action). We finished the migration a week inside the deadline, and the stand-up became how the team ran every project after that (result)."

Resilience: a time something went wrong

"Tell me about a time you failed or made a mistake."

What good looks like:

A real mistake you own, with no blame shifted onto others
The specific action you took to put it right
A result that shows the lesson stuck

Model answer: "I sent a client report with an error in the headline figure (situation). It was my analysis, so it was my mistake to fix (task). I called the client within the hour, walked them through the corrected number, and then built a second-checker step into our process so two people sign off any client-facing figure (action). The client stayed, told us the quick honesty mattered, and we have not shipped a figure error since (result)."

Your sharpest raw material for answers like these sits on your CV, because most behavioural questions are an invitation to expand a single line of it. If the line is vague, the answer starts vague, so it is worth getting both right together. Practising these answers out loud, against the questions your specific role invites, is where preparation turns into composure: that is exactly what AI interview coaching is built to do.

Why prepared stories beat memorised scripts

The instinct is to write a perfect answer for every likely competency question and memorise it word for word. That instinct backfires. A script collapses the moment the question arrives in a slightly different shape, and competency questions almost always do, because the same competency can be probed a dozen ways.

The better preparation is a small bank of flexible stories. Pick five or six episodes from your experience that are rich enough to evidence more than one competency. The stakeholder story above, for instance, can answer questions about pressure, conflict, communication and ownership, depending on which part you lead with.

Then, in the room, you are not retrieving a memorised paragraph. You are choosing which story fits and which competency to foreground, and telling it in STAR shape on the spot. That is far more robust, and it sounds like a person rather than a recital.

One honest note on rehearsal. Reading your stories silently feels like preparation, but it hides the two failures that cost most marks: rambling situations and answers that never reach a result. The only fix is to say them aloud, ideally against questions built from the role you actually applied for, so the practice matches the real thing. If you are still working out which roles to chase, start with our guide to finding a job that fits.

Frequently Asked Questions

The basics

What is the STAR method in an interview?

STAR is a four-part structure for answering competency interview questions: Situation, Task, Action, Result. You set the scene in a sentence, state what you were responsible for, describe what you personally did, and finish with the measurable outcome. It keeps a behavioural answer to the point and makes sure you reach a result rather than trailing off.

What are competency based interview questions?

Competency based interview questions ask for a real past example of a behaviour, usually opening with phrases like give me an example of a time when or tell me about a situation where. They test competencies such as teamwork, problem solving, leadership and resilience on the assumption that past behaviour predicts future behaviour. They are standard on UK graduate schemes and across the public sector.

Preparing and delivering

How do I prepare for a competency based interview?

Read the job description and list the competencies it names, then prepare five or six flexible stories from your experience that each cover two or three of them. Write each story in STAR shape and rehearse it out loud, because spoken answers expose the rambling that silent reading hides. Prepare stories rather than scripts, so one example can be reshaped to fit several questions.

What if I do not have a strong example for a competency question?

Widen where you look. Volunteering, study projects, part-time work and side projects all count, because the interviewer is testing the behaviour rather than the setting. If you genuinely lack the experience, describe how you would approach the situation and a near example that shows the same instinct. An honest adjacent answer beats an invented one that falls apart under follow-up questions.

How long should a STAR answer be?

Aim for 90 seconds to two minutes. Spend one sentence on the situation and task, give most of the time to the action, which is the part the interviewer is scoring, and close on a clear result. If an answer runs much longer it usually means the situation was over-explained, so trim the setup, not the result.

Conclusion: structure first, then practise

Competency interview questions are the most preparable part of any interview, the STAR method turns a vague story into a scored answer, and a small bank of flexible stories beats a folder of memorised scripts every time. Read the job description for the competencies, build your stories in STAR shape, and rehearse the ones you dread out loud. For the questions outside the behavioural ones, step back to the full guide to interview questions and answers.

Ready to practise your STAR answers?

TalentAid turns the competencies in a real job description into a mock interview built for the role you want.

Start free and practise out loud