Competency Based Interview Questions: Examples and How to Answer

Competency based interview questions are the questions employers use to test whether you have actually done the things a job requires — not whether you can talk about them in theory. Instead of asking “Are you a good team player?”, an interviewer asks “Tell me about a time you worked with a difficult team member.” Your answer must be a real story from your past, because the whole method rests on one idea: past behaviour is the best predictor of future behaviour.

This format is standard in the UK civil service, large graduate schemes, the NHS, banks, and a growing number of private companies worldwide. If you have an interview with any large organisation, you should expect at least part of it to be competency based. This guide explains how the scoring works, lists the competencies employers test most often with real example questions, and shows you how to build answers that score at the top of the scale.

What Is a Competency Based Interview?

A competency based interview (also called a behavioural or structured interview) is built around a fixed list of competencies — the skills, behaviours, and qualities the employer has decided the job needs. Typical lists include teamwork, communication, problem solving, leadership, organisation, adaptability, and customer focus.

Every candidate for the same role is asked the same core questions, and every answer is scored against the same marking guide. That structure is deliberate: it makes hiring fairer and more consistent, and it means your preparation can be unusually precise. You are not guessing what a friendly chat might cover — you are preparing evidence for a known list of skills.

The questions almost always start with phrases like:

• “Tell me about a time when…”
• “Describe a situation where…”
• “Give me an example of…”
• “Talk me through how you…”

When you hear one of those openers, the interviewer does not want your opinion or a general claim. They want one specific, real example, told in enough detail that they can score what you personally did.

How Scoring Works (and Why It Matters for Your Answers)

Most competency interviews score each answer on a simple scale, often 1 to 5 or 1 to 7. A top-scoring answer has four features:

1. It is specific. One real occasion, with a clear beginning, middle, and end — not “I usually…” or “In my last job I often…”
2. It is personal. The panel scores what you did. Answers full of “we decided” and “the team handled it” score low because your individual contribution is invisible.
3. It shows the competency at the right level. A supervisor role needs examples of organising others, not just yourself. Match the scale of your example to the scale of the job.
4. It ends with a result and a reflection. What happened because of your actions, and what you learned or would do the same way again.

Knowing this changes how you prepare. You do not need fifty stories. You need six to eight strong, specific stories that you can adapt, each one told with your own actions in the centre. That is why competency based interview questions reward preparation more than polish.

The STAR Method: The Structure Behind Every Strong Answer

Almost every good competency answer follows the STAR structure:

• S — Situation: Set the scene in one or two sentences. Where were you, what was happening, why did it matter?
• T — Task: What was your responsibility? What were you trying to achieve?
• A — Action: What did you do, step by step? This should be the longest part of your answer — around 60–70% of it.
• R — Result: What happened? Quantify it if you can, and add one line about what you learned.

Keep the whole answer to about two minutes when spoken. If you are new to this structure, practise it on one story until it feels natural, then reuse the same skeleton for every other competency. Our companion guide to behavioral interview questions works through more question-by-question examples you can borrow the shape from.

The Most Common Competencies and Example Questions

1. Teamwork

Employers want evidence that you support colleagues, share credit, and handle friction constructively.

Example questions:

• Tell me about a time you worked as part of a team to achieve a goal.
• Describe a time you disagreed with a team member. How did you resolve it?
• Give an example of when you helped a colleague who was struggling.

What a strong answer shows: you listened, you did your share and a little more, you dealt with disagreement by focusing on the shared goal, and the team succeeded partly because of your contribution.

2. Communication

This covers explaining things clearly, listening, adapting your message to your audience, and handling difficult conversations.

Example questions:

• Tell me about a time you had to explain something complicated to someone.
• Describe a situation where you had to deliver bad news.
• Give an example of when you persuaded someone to your point of view.

What a strong answer shows: you thought about what the other person needed, chose the right channel and tone, checked understanding, and achieved a clear outcome.

3. Problem Solving

Interviewers look for a logical approach: define the problem, consider options, act, and review.

Example questions:

• Tell me about the biggest problem you have solved at work.
• Describe a time something went wrong. What did you do?
• Give an example of when you found a better way of doing something.

What a strong answer shows: you stayed calm, gathered facts before acting, weighed more than one option, and your solution worked — ideally with a measurable improvement.

4. Leadership and Taking Initiative

You do not need to have managed people to score well here. Leading a small task, volunteering, or stepping up in a gap all count.

Example questions:

• Tell me about a time you took the lead on something.
• Describe a situation where you motivated others.
• Give an example of when you went above and beyond what was expected.

What a strong answer shows: you saw what needed doing without being asked, organised people or resources, made decisions, and took responsibility for the outcome.

5. Organisation, Planning, and Time Management

This competency is about juggling deadlines and priorities without dropping anything.

Example questions:

• Tell me about a time you had to meet a tight deadline.
• Describe how you handled having several urgent tasks at once.
• Give an example of a project you planned from start to finish.

What a strong answer shows: you prioritised deliberately, used a system (list, plan, calendar), communicated early when something was at risk, and delivered on time.

6. Adaptability and Resilience

Change is constant in most workplaces, so panels test how you respond when plans break.

Example questions:

• Tell me about a time your plans had to change suddenly.
• Describe a setback you faced and how you dealt with it.
• Give an example of when you received critical feedback. What did you do with it?

What a strong answer shows: you stayed constructive, adjusted quickly, learned from the setback, and can point to a later situation where you applied that lesson.

7. Customer Focus and Service

For any role dealing with the public, clients, patients, or internal customers, this competency is central.

Example questions:

• Tell me about a time you dealt with a difficult or unhappy customer.
• Describe how you have gone out of your way to help a customer.
• Give an example of when you turned a complaint into a positive outcome.

What a strong answer shows: you listened without interrupting, took ownership instead of blaming others, fixed what you could, followed up, and the customer left satisfied.

8. Decision Making

Panels want to see that you can judge a situation, choose a course of action, and stand behind it.

Example questions:

• Tell me about a difficult decision you had to make.
• Describe a time you had to decide quickly with limited information.
• Give an example of a decision that did not work out. What did you learn?

What a strong answer shows: you gathered the information that was realistically available, considered the risks, decided, communicated the decision, and reviewed the result honestly.

A Worked Example Answer

Question: “Tell me about a time you had to meet a tight deadline.”

Answer (STAR): (Situation) “In my retail job last Christmas, our store’s stock delivery arrived two days late during the busiest week of the year, and the regional manager still expected the sale display finished by Friday opening.”

(Task) “As the most experienced assistant on shift, I was responsible for getting the display built without closing any aisles during trading hours.” (Action) “I listed everything the display needed, split it into tasks that could be done before opening and tasks that could be done in quiet periods, and asked two colleagues to come in thirty minutes early with me on the Thursday — which our supervisor approved. I built the frame and pricing first, because everything else depended on them, and kept a short checklist on the till so anyone free could pick up the next task.”

(Result) “The display was finished an hour before opening on Friday, and that weekend the promoted line sold out. My manager later used the checklist idea for the January sale. I learned that breaking a deadline into dependent steps — what must happen first — is what makes a tight deadline feel manageable.”

Notice how little of that answer is “we”: the actions, the system, and the learning all belong to the candidate. That is what scores.

How to Prepare in One Week

1. Get the competency list. It is often in the job description or person specification. Highlight every behaviour word — “communicate”, “organise”, “resolve” — those are your competencies.
2. Build a story bank. Write down six to eight real examples from work, study, volunteering, sport, or family responsibilities. For each, note the situation, your actions, and the result in bullet points.
3. Map stories to competencies. Most good stories cover two or three competencies each. A story about rescuing a group project can serve teamwork, problem solving, and organisation.
4. Write STAR bullets, not scripts. Memorised scripts sound robotic and collapse under follow-up questions. Bullets keep you accurate and natural.
5. Practise out loud. Say each answer once or twice, timed. Aim for about two minutes per answer.
6. Prepare for follow-ups. Panels often probe: “What exactly did you say?” “What would you do differently?” Honest, specific answers score well.
7. Research the employer. Knowing their values helps you choose which stories to lead with — and most competency frameworks are published on the employer’s own website, so read it there first. You can also check typical duties in the Occupational Outlook Handbook.

If you are preparing more broadly, work through our guide to common interview questions and answers as well, because most interviews mix competency questions with general and motivational ones.

Common Mistakes That Cost Marks

• Answering hypothetically. “I would…” instead of “I did…” is the single most common reason for a low score. The method scores evidence, not intentions.
• Using “we” throughout. Panels cannot score a contribution they cannot see. Say what the team did in one line, then spend the answer on your actions.
• Choosing a vague or routine example. “Every day I deal with customers” is not an example. Pick one memorable occasion with stakes and a result.
• Skipping the result. Answers that trail off after the actions leave the panel guessing whether anything worked. Always close the story.
• Rambling through the situation. Long scene-setting eats your two minutes. Keep the situation to two sentences and spend your time on actions.
• Inventing examples. Experienced panels probe details, and fabricated stories unravel quickly — and dishonesty in a structured interview is usually an automatic fail. A modest true example always beats a dramatic false one.
• Repeating the same story for every question. Panels notice, and each answer is scored on how well it matches that competency. Adapt or choose a different example.

What If You Have No Work Experience?

Use study, volunteering, sports, caring responsibilities, or community roles — panels accept these readily for entry-level and graduate roles, because the competency is what matters, not the setting. Organising a revision group is planning. Handling a complaint at a charity shop is customer service. Captaining a team through a losing season is resilience and leadership. Choose the example where your personal actions are clearest, whatever the setting.

Quick Preparation Checklist

• Competency list extracted from the job description or person specification
• Six to eight real examples written as STAR bullets
• Each example mapped to the competencies it can serve
• Answers practised out loud, about two minutes each
• One example ready for a failure or setback question, ending in what you learned
• Employer’s values and competency framework read on their official site
• Two thoughtful questions prepared to ask at the end

Frequently Asked Questions

What is the difference between competency based and behavioural interview questions?

Very little in practice. The two terms describe the same method: questions that ask for real past examples as evidence of a skill. “Competency based” is the more common term in the UK and in public-sector hiring; “behavioural” is more common in the US. The STAR answer structure works for both.

How many competency questions will I be asked?

Typically one question per competency, with four to eight competencies in a full interview — so expect roughly four to eight main questions, plus follow-up probes on some of them. Panel interviews for graduate schemes and public-sector roles sit at the higher end of that range.

How long should a competency answer be?

About two minutes of speaking is the sweet spot: long enough to cover situation, task, actions, and result with real detail, short enough to stay focused. Much under a minute usually means missing detail; much over three minutes usually means the situation or the story has taken over from your actions.

Can I use the same example for two different questions?

You can, but adapt it: emphasise different actions for each competency, and only reuse a story if it genuinely fits both. Panels score each answer against its own competency, so a teamwork retelling of a problem-solving story must foreground what you did with and for other people, not just the fix.

What if I cannot think of an example during the interview?

Ask for a moment to think — panels expect it and it costs nothing. Search your story bank by setting rather than by competency: work, study, volunteering, sport. If you truly have no direct example, say so honestly, offer the closest related experience you have, and explain what you learned from it. Never invent one.

Conclusion

Competency based interview questions reward one thing: clear, honest evidence. Learn the competencies from the job description, build a small bank of real stories, structure each answer with STAR, keep your own actions at the centre, and always finish with the result and what you learned. Do that, and the format stops being a test you fear and becomes what it was designed to be — a fair chance to show what you have actually done. Treat every answer as evidence, and competency based interview questions become far less daunting.