Competency-Based Interview Questions (UK): What Each Question Tests and How to Answer With Your Own Evidence

Competency-based interview questions ask you to describe a real time you used a specific skill, such as teamwork, problem solving or handling pressure. Each question is testing one competency from the job, and the interviewer scores your answer on the evidence you give: what the situation was, what you personally did, and what happened as a result. To answer well, work out which competency the question is testing, pick one true story from your own experience that shows it, and tell it in STAR order with most of your time on your actions.

Most guides stop at a list of questions. This one maps common UK competency questions to the competency behind each one, then shows you how to choose evidence from your own work to answer it.

What a competency-based interview is

A competency-based interview is a structured interview where most questions ask for past examples rather than opinions or hypotheticals. Instead of "How would you handle a difficult customer?", you hear "Tell me about a time you dealt with a difficult customer."

The idea is that what you have done before is the best guide to what you will do next. The employer decides in advance which competencies matter, writes questions to test each one, and scores every candidate against the same criteria.

You will also see these called behavioural interviews, and the questions called behavioural interview questions. In practice the terms overlap almost completely. Some UK employers say "competencies", some say "behaviours", and some say "values", but the format is the same: a prompt that starts with "Tell me about a time", "Describe a situation" or "Give an example of".

A competency, in this sense, is a skill or behaviour the job needs, written so it can be observed. "Communication" on its own is vague. "Explains complex information clearly to people without specialist knowledge" is a competency an interviewer can listen for.

You will usually find the competencies in one of three places:

• The person specification, often split into essential and desirable criteria.
• The job description, in lines like "builds effective relationships" or "manages competing priorities".
• A named framework, which some employers and sectors use across every role. If the advert names one, use its wording.

If you can see the list, you can predict most of the questions.

How interviewers score you: evidence, not polish

In a structured competency interview, the panel usually has a scoring guide for each question. The details vary between employers, but the guides tend to reward the same things:

• A specific example. One real situation, with a time and a place, not "I always..." or "I would...".
• Your own actions. What you did, in enough detail to picture it. "We" is fine for context, but the score comes from "I".
• A result. What changed, and ideally how you know. A number helps if it is true. A decision, a deadline met, or feedback from a named person also counts.
• Relevance to the competency. The story has to show the skill the question was testing. A strong story about the wrong competency can score poorly.
• Reflection, sometimes. For higher-level roles, panels often listen for what you learned or would do differently.

What they are usually not scoring is how fluent you sound. A plain answer with clear evidence will normally beat a polished one that stays general, which is good news if you get nervous.

Common competency-based interview questions and what each one tests

The table below lists questions that come up often in UK interviews, the competency each one is usually testing, and an evidence cue: the kind of story from your own experience that tends to answer it well.

Two things to notice.

First, several questions overlap. "Disagreed with a colleague" and "persuaded someone" can both take an influencing story, so use the advert's wording to decide which angle to stress.

Second, the question wording does not always name the competency. "Tell me about a time you went beyond what was expected" is rarely about working long hours. It is usually about initiative: noticing something and acting on it.

How to map each competency to a story from your bank

A question list tells you what might be asked. A map tells you what you will say. Building one takes about an hour the first time.

Step 1: list the competencies for this job. Take them from the person specification or the job description, in the employer's own words. Most roles have four to eight. If the advert is long, start with anything marked essential or assessed at interview, then any behaviours repeated more than once.

Step 2: turn each competency into one or two likely questions. Use the table above as a starting point. "Builds effective relationships" becomes "Tell me about a time you worked with someone difficult" or "Give an example of working across teams".

Step 3: pick one main story for each competency. If you keep a STAR story bank, search its competency tags. If you do not have one yet, your CV is the quickest place to start: each bullet point is a story with the detail removed, and this guide to turning CV bullets into interview stories shows how to unpack them.

Step 4: add a backup story. Panels often ask "Can you give me another example?", and sometimes the question you expected comes out slightly differently. A second story means you are not forced to stretch the first.

Step 5: check the spread. No story should cover more than two competencies in the same interview. If one project keeps coming up, the panel may wonder what else you have done.

A simple worksheet is enough:

When choosing between stories, a few rules help:

• Pick the clearest, not the biggest. A small piece of work where your part was obvious usually scores better than a large programme where you were one of many.
• Prefer recent. A story from the last two or three years is easier to recall in detail and easier to defend in follow-up questions.
• Match the level. For a team leader role, a story where you coordinated others will score higher on leadership than one where you were coordinated.
• Look beyond paid work if you need to. Volunteering, caring, study and side projects all count, as long as your part is clear.
• Mark the gaps honestly. If a competency has no story, that is a prompt to look harder now, not to invent one on the day.

Sample answer structure: STAR with the competency named

STAR stands for Situation, Task, Action and Result. For competency questions, one small addition makes a big difference: name the competency in your first sentence, so the panel knows straight away what your example is evidence of. If you want the method itself in more depth, the STAR method guide covers each part with timings.

A useful shape for a two-minute answer:

1. Signpost (one sentence). Name the competency or the theme of the question. "A good example of managing competing priorities is from last winter."
2. Situation and Task (about 20 percent). Just enough context to follow the story. Where, when, and what you were responsible for.
3. Action (about 60 percent). Three to five specific steps, each starting with "I". This is where most of the score comes from.
4. Result (about 20 percent). What changed, and how you know.
5. Link back (optional, one sentence). What you learned, or how it applies to this role.

Worked example (invented and illustrative, not a real person or employer). The question is "Tell me about a time you managed competing priorities."

"A good example of managing competing priorities is from my role as an operations coordinator at a regional charity. In the same week, I was asked to prepare figures for a funder report, organise a volunteer training day, and cover the office manager's inbox while she was on leave.

I was responsible for all three, and the funder report had a fixed deadline that affected our grant.

First, I listed every task with its deadline and who it affected. I saw the funder report could not move, but the training day had some flexibility on preparation. I spoke to the volunteer lead that morning and agreed I would send the training pack on Thursday instead of Tuesday, which still gave volunteers two days' notice. For the inbox, I set up a short auto-reply with expected response times and checked it twice a day rather than constantly. I then blocked out two mornings for the funder figures, with my phone on silent.

The funder report went in a day early, the training day ran as planned with every volunteer having the pack in advance, and no urgent email was missed. Since then I have kept the same task list for busy weeks, and I think that habit would be useful in this role, where the job description mentions frequent overlapping deadlines."

Notice what the answer does. The competency is named in the first line. The context is short. Most of the time goes on specific actions, each with a reason. The result is specific without needing a made-up percentage.

Mistakes that kill competency answers

Answering hypothetically. "I would always prioritise by deadline" describes a belief, not evidence. If you catch yourself saying "I would", stop and give a real example.

Describing what the team did. "We delivered the project on time" tells the panel nothing about your part. Use "we" for context and "I" for actions.

Choosing a story for the wrong competency. A brilliant story about technical problem solving will not score well on a question about teamwork. Check which competency the question is testing before you choose.

No result, or a vague one. "It went well" is not a result. Name what changed. If you are not sure of a figure, describe the outcome in plain terms rather than guessing a number.

Using the same story for everything. One strong project can cover two competencies. If it covers five, the panel hears the same example repeatedly.

Inventing or stretching. Follow-up questions such as "What did your manager say?" or "What would you do differently?" tend to expose stories that are not quite true. An honest smaller example is safer and usually scores better.

Freezing on an unfamiliar question. A short pause, then restating the competency you think they are testing, often brings the right story back. See our guide on what to do when your mind goes blank in an interview.

Role and sector notes

The format is broadly the same everywhere, but some UK sectors have their own frameworks and wording. A few pointers:

• NHS roles. Many NHS employers use values-based interview questions alongside competency questions, linked to the values in the NHS Constitution. Expect questions about patient care, respect and working together. Read the trust's own values on its website and tag your stories with them.
• Police roles. Police forces in England and Wales commonly assess against the College of Policing's Competency and Values Framework. Check the current version and the force's own guidance before you prepare.
• Civil Service roles. The Civil Service uses its own recruitment framework, and the details have changed over time. Use the wording in the specific job advert and the current guidance on gov.uk rather than an old question list.
• Private sector and graduate schemes. Many private employers call these behavioural questions and do not publish a framework, so the job description is your best guide.

In every case, the method is the same: find the employer's list, use their words, and map one real story to each item.

FAQ

How do you pass a competency-based interview?

Find the competencies the role is assessing, usually in the person specification or job description. Prepare one true story and one backup for each. In the interview, name the competency in your first sentence, tell the story in STAR order with most of your time on your own actions, and finish with a specific result. Panels score evidence, so a clear, honest example matters more than sounding polished.

What are examples of competency-based questions?

Common examples include "Tell me about a time you worked as part of a team", "Describe a time you disagreed with a colleague", "Give an example of when you met a tight deadline", "Tell me about a mistake you made" and "Give an example of when you improved a process". The table above lists more than twenty, with the competency each one usually tests.

How long should a competency-based answer be?

Around two minutes is a good target for most questions. That is long enough for context, several specific actions and a result, and short enough for the panel to follow. If you are going much past three minutes, you are probably spending too long on the situation.

Are competency-based and behavioural interview questions the same?

In practice, yes. Both ask for real past examples and are scored on what you actually did. UK employers may call them competency, behavioural or values-based questions depending on the sector, but you prepare for them in the same way.

What if I do not have an example for a competency?

Look again with the competency in mind, including smaller and non-work examples. If there is still nothing, say so honestly, give the closest example you have, and explain how you would approach that situation in the role. That usually lands better than a stretched story.

Keeping your evidence ready for the next interview

A spreadsheet works for all of this, and the worksheet above is enough to get started. The slow part is keeping every story written up and tagged by competency, so you can map the next job quickly instead of starting from memory each time.

That is the part Career Canvas is built for. Send your CV and every project becomes a STAR story, laid out on one screen. Pick a competency, such as stakeholder management, and the stories that fit light up, each with a one-line reason why. Nothing is invented: a result only appears where you can back it up, and you approve every word. If that would save you an hour before your next competency interview, you can see an example canvas or get started free.