Learn what competency interviews are testing: real past behaviour, not opinions.
Job applications
How to Answer Competency Interview Questions (STAR)
A clear guide to UK competency interviews and the STAR method: what it means, a full worked example, common questions, and mistakes to avoid.
Build a story bank of six to eight strong examples from work, study, or projects.
Answer each question using the STAR structure: Situation, Task, Action, Result.
Spend most of your answer on your Actions, and keep the Situation short.
End every answer with a clear, ideally measurable, Result.
Practise aloud and prepare for follow-up questions about your decisions.
Short answer
STAR stands for Situation, Task, Action, and Result. UK employers use competency questions to see how you have behaved in real situations, because past behaviour is a good guide to future behaviour. Pick a relevant example, set the scene in one or two sentences, focus most of your answer on what you personally did, and finish with the outcome. Questions usually start with "Tell me about a time when…" or "Give me an example of…". STAR gives you a calm, repeatable way to answer them well.
What a competency interview is
A competency interview, sometimes called a behavioural or structured interview, asks you to describe specific things you have actually done. Instead of "Are you a good team player?", you get "Tell me about a time you worked in a difficult team." Employers use this style because it is harder to bluff. Anyone can claim to be organised. Describing a real situation where you organised something, and what happened, is far more convincing. Many UK employers, including the NHS, the Civil Service, banks, and large graduate schemes, score these answers against a fixed list of competencies. That means a clear, structured answer is easier for them to mark and easier for you to deliver.
What STAR stands for
Situation: set the scene briefly. Where were you, and what was happening? One or two sentences is enough. Task: explain what you needed to do, or the problem you had to solve. What was your responsibility in that moment? Action: this is the heart of the answer. Describe the specific steps you took, and why. Use "I", not "we", because the interviewer is assessing you. Result: explain what happened. Use a number, a saved cost, positive feedback, or a delivered outcome where you can. If the result was mixed, say what you learned.
Why most of the answer should be your actions
A common mistake is spending too long describing the situation and too little on what you did. The interviewer is scoring your behaviour, so your actions matter most. A useful balance is roughly: Situation and Task together about a quarter of the answer, Action about half, and Result the final quarter. Keep the background tight and get to your decisions quickly. Use "I" deliberately. In team stories it is tempting to say "we", but the interviewer cannot score the team. Say what you personally suggested, decided, built, or handled, even when others were involved.
How to build a story bank
Before any interview, prepare six to eight strong stories from work, study, volunteering, or personal projects. Each one should be flexible enough to answer several different questions. For each story, note the situation, your task, your specific actions, and the result. Then tag it with the competencies it proves: teamwork, problem-solving, leadership, handling pressure, dealing with conflict, meeting a deadline, learning something new, or improving a process. When a question comes up, you pick the closest story and shape it to fit. This is far calmer than inventing an example on the spot. To choose which competencies to prepare, re-read the job advert and note the behaviours it repeats.
A full worked example
Question: "Tell me about a time you handled a tight deadline." Situation: "In my final university year, our group project partner dropped out two days before a client presentation." Task: "I had to cover their research section and still deliver the full presentation on time, without lowering quality." Action: "I split the missing work into three parts and reassigned two to teammates based on their strengths. I took the hardest section myself. I set a shared checklist, ran a one-hour catch-up that evening, and built in time to rehearse the next morning. I also messaged the client to confirm the agenda so there were no surprises." Result: "We delivered on time. The client gave us the top mark in the cohort and asked for our slides as a template. I learned to plan for a teammate dropping out, so now I always agree backup owners early." That answer is short on background, heavy on actions, and ends with a clear result and a lesson.
Common competencies and questions to prepare
Teamwork: "Tell me about a time you worked with a difficult colleague." Show how you stayed professional and found a way forward. Problem-solving: "Describe a problem you solved creatively." Show your thinking, not just the outcome. Handling pressure: "Give an example of working under pressure." Show that you stayed calm and prioritised. Leadership: "Tell me about a time you led without being the manager." Influence counts as leadership. Conflict: "Describe a disagreement and how you resolved it." Show that you listened and focused on the goal, not on winning. Failure: "Tell me about a time something went wrong." Be honest, take ownership, and explain what changed afterwards.
How long should each answer be
Aim for around 90 seconds to two minutes per answer. Long enough to show depth, short enough to hold attention. If the interviewer wants more, they will ask a follow-up. Practise hitting the result before you run out of time. Many candidates trail off in the action and never state the outcome, which is the part interviewers most want to hear.
Handling the "weakness" and "failure" questions
These trip up many people. The trick is honesty plus growth. Pick a real, moderate weakness, then explain the concrete steps you are taking to manage it. Avoid fake weaknesses like "I work too hard". They sound rehearsed. Equally, do not confess something that would stop you doing the job. Choose something genuine, then show self-awareness and progress. For failure questions, own your part clearly, avoid blaming others, and focus the result on what you learned and changed. Interviewers respect candidates who can reflect.
Mistakes that lower your score
Telling a story with no result. Spending too long on background. Saying "we" instead of "I". Choosing an example that does not match the competency asked. Rambling without structure. Another common one is using a single story for everything, even when it does not fit. A varied story bank prevents this. So does listening carefully to the exact competency in the question before you start.
How to practise
Practise aloud, not just in your head. Record yourself or ask a friend to listen. Check that your situation is short, your actions are specific, and your result is clear. You can use AI to generate likely questions from a job description, then answer in your own words. Ask it to throw skeptical follow-ups at you, such as "Why did you choose that approach?" Preparing for follow-ups is what separates a good answer from a great one. For interviews where AI is part of the process itself, see our guide on preparing for AI-assisted interviews.
Bringing it together before the interview
Once your CV is sharp and your shortlist is focused, your interview prep becomes simpler: match each saved role to the competencies it needs, then choose the best story for each. Build that shortlist with the Sponsio jobs feed, and use how to compare UK employers before you apply to research the companies you reach interview stage with. When your evidence is organised, competency interviews stop feeling like a memory test and start feeling like a structured conversation you are ready for.
Common questions
What candidates usually need to confirm
What does STAR stand for in interviews?
STAR stands for Situation, Task, Action, and Result. It is a four-part structure for answering competency questions clearly: set the scene, explain your responsibility, describe what you did, and state the outcome.
What is a competency-based interview?
It is an interview where you describe specific past situations to show skills like teamwork or problem-solving. Questions usually begin "Tell me about a time when…". Employers score your answers against a fixed list of competencies.
How long should a STAR answer be?
Around 90 seconds to two minutes. Keep the situation brief, spend most of the time on your actions, and always finish with a result. If they want more detail, they will ask a follow-up.
Should I say "I" or "we" in my answers?
Use "I" for the parts you personally did, even in team stories. The interviewer is assessing you, not the group, so they need to hear your specific decisions and actions.
How many stories should I prepare?
Six to eight flexible stories covering common competencies: teamwork, problem-solving, leadership, pressure, conflict, and a setback. Each can usually be reshaped to answer several different questions.
Can I use the STAR method if I have little work experience?
Yes. Use examples from university projects, volunteering, part-time jobs, sport, or personal projects. The structure is the same. What matters is a clear situation, your specific actions, and a real result.