If you have ever been asked "Tell me about a time when..." in an interview, you have met a competency-based question. They are common in UK interviews, from graduate schemes and public sector roles to retail, healthcare and office jobs.
The good news is that they are predictable once you know how they work. This guide explains what interviewers are looking for, how the STAR method gives your answer a clear shape, and how to build your own examples, even if you have limited work experience.
What are competency-based interview questions?
A competency is a skill or behaviour needed to do the job well. Examples include teamwork, communication, problem-solving, organisation and dealing with pressure.
Instead of asking what you would do, the interviewer asks what you have done. The idea is that past behaviour is a good guide to future behaviour. Typical questions look like this:
- Tell me about a time you worked as part of a team to reach a goal.
- Describe a situation where you had to deal with a difficult customer.
- Give an example of when you had to meet a tight deadline.
- Tell me about a time you made a mistake. What did you do?
- Describe a time you had to learn something new quickly.
Every employer scores answers against a set of criteria, often agreed before the interview. That is why two candidates may be asked the same questions in the same order. Your job is to give evidence, not opinions.
Where to find the competencies they want
You can prepare before you are invited. Look at the job advert, the job description and the person specification, if there is one. Phrases such as "works well under pressure", "strong communication skills" or "attention to detail" are clues to what you will be asked about.
Many public sector and larger organisations publish a framework of behaviours or values. If the employer has one, read it and think about how your examples match.
The STAR method explained
STAR is a simple structure for answering competency questions. It stops you rambling and makes sure you include the parts the interviewer needs.
- Situation: Set the scene briefly. Where were you and what was happening?
- Task: Explain your responsibility or what needed to be achieved.
- Action: Describe what you did, step by step.
- Result: Say what happened, what you learned, and what you would do again or differently.
A useful rule of thumb is to spend about 10 to 20 per cent on Situation and Task together, around 60 per cent on Action, and the rest on Result. Most people do the opposite and spend too long on background.
Say "I", not just "we"
Teamwork is great, but the interviewer is hiring you, not your old team. Explain what the group did, then be clear about your own contribution. "I suggested", "I arranged" and "I checked" are far more useful than "we sorted it out".
Worked example 1: dealing with a difficult customer
Question: Tell me about a time you dealt with a difficult customer.
Situation: "I was working a Saturday shift in a busy shop when a customer came to the till angry that a refund had been refused the week before."
Task: "I needed to calm things down, find out what had happened and make sure the queue behind them wasn't left waiting."
Action: "I stayed calm and let them explain without interrupting. I apologised for the frustration, then checked the refund policy and the notes on the system. I explained clearly what we could and couldn't do, and offered an exchange. I asked a colleague to cover my till so I could finish the conversation properly."
Result: "The customer accepted the exchange and thanked me before leaving. My manager asked me to share how I handled it with newer staff. I learned that listening first usually reduces tension quickly."
Worked example 2: meeting a tight deadline
Question: Describe a time you had to meet a tight deadline.
Situation: "In my final year at university, I had two assignments due within three days of each other, as well as a part-time job."
Task: "I needed to submit both on time without letting the quality drop."
Action: "I listed everything that remained and estimated how long each part would take. I swapped two shifts with a coworker, blocked out focused study time each evening and switched off notifications. I finished the first draft of the earlier assignment a day early so I had time to proofread it."
Result: "I handed in both on time and received good feedback on the structure. Since then I always break big tasks into smaller steps with mini deadlines."
Notice that neither example claims a dramatic win. They are realistic, specific and show the person's own actions. That is what interviewers want.
Worked example 3: when something went wrong
Question: Tell me about a time you made a mistake.
Situation: "I was helping to organise a volunteer rota and I accidentally double-booked two people for the same slot while leaving another empty."
Task: "I needed to fix it before the event and make sure it didn't happen again."
Action: "As soon as I spotted it, I told the coordinator, then contacted both volunteers to apologise and ask if one could move. I offered a swap to a time that suited them. I then created a simple checklist to check the rota against availability before sending it out."
Result: "The slot was covered and the event ran smoothly. The checklist was later used for other rotas. I learned to flag errors early rather than hoping they would go unnoticed."
Honest answers about mistakes work well when you show accountability and what you changed afterwards.
No work experience? Use other examples
You do not need a paid job to answer well. Strong examples can come from:
- School, college or university projects and group work
- Volunteering or community activities
- Sports teams, clubs and societies
- Caring for family members or managing household responsibilities
- Hobbies, such as organising events or running an online group
The interviewer cares about the skill you show, not where it happened. If you are changing careers, choose examples that match the competencies in the new role, even if they come from a different industry.
How to prepare in five steps
- Pick the competencies. Note five or six from the job description.
- Collect examples. Write down two or three situations from work, study or life that fit each one.
- Write them in STAR form. Short bullet points are enough. Do not memorise a script.
- Say them out loud. Time yourself. Aim for around two minutes per answer.
- Reuse and adapt. One good example can often answer several questions, such as teamwork, communication and problem-solving, by changing the focus.
Common mistakes to avoid
- Being vague. "I usually try to stay calm" is an opinion. A specific story is evidence.
- Spending too long on the situation. Get to your actions quickly.
- Leaving out the result. Always say what happened, even if the outcome was modest.
- Choosing a story that makes you look bad without a lesson. If you share a mistake, show what you changed.
- Blaming others. Stay factual and professional about colleagues and managers.
If your mind goes blank
It is fine to pause. Say, "Let me think of a good example," and take a few seconds. Interviewers would rather wait than hear a rushed, unclear answer. If you are interviewing online or by phone, keeping a page of bullet-point prompts nearby can help, as long as you do not read from it word for word.
If you realise partway through that your example is not working, it is acceptable to say so and offer a different one.
Final tips
Keep your tone natural and friendly. The structure is there to support you, not to make you sound robotic. Take a moment at the end to link your answer to the job, for example: "That experience would help me when handling busy periods in this role."
After each interview, write down which questions came up and which examples worked well. Over time you will build a bank of tried-and-tested stories, and competency questions will feel far less daunting.
