Competency based interview questions ask you to prove you've already demonstrated the skills the role needs. The interviewer gives you a prompt like "Tell me about a time you worked under pressure," and you answer with a real past example structured around STAR: Situation, Task, Action, Result. Not a hypothetical. Not "I would usually handle it by…" A specific story from your work, studies, or volunteering, delivered in 90 to 120 seconds, with most of your time spent on what you personally did.
That is the whole format. Everything else in this guide is about doing it well enough to get scored.
If you've applied for a Civil Service role, an NHS band, a graduate scheme, or any large UK employer with a formal HR function, you've almost certainly seen this setup. The interviewer has a competency list from the job description and a scoring sheet. Your job is to give them evidence they can mark.
What Is a Competency Based Interview?
A competency based interview is a structured interview where each question maps to a specific skill or behaviour the employer has decided matters for the role. Communication. Teamwork. Leadership. Problem-solving. Handling conflict. Making decisions under pressure.
The logic is straightforward: past behaviour predicts future performance better than hypotheticals or unstructured chat. The CIPD notes that competency-based selection remains one of the most widely used structured interview approaches in UK hiring.
It differs from an unstructured interview, where recruiters ask open-ended questions like "Why do you want this job?" to get a general impression. A competency based interview is more systematic. Each question targets a skill. Your answers get compared against pre-set criteria and marked.
You may also hear it called a behavioural interview, situational interview, or structured interview. Same question style in most cases. The difference is usually whether the employer publishes the competency framework upfront and scores you formally against it.
Key Competencies Employers Look For
Employers pick competencies from the job description, but most roles pull from the same pool. If you prepare stories for these eight, you'll cover the majority of competency based interview questions you'll face.
| Competency | What they're testing |
|---|---|
| Teamwork | Collaboration, contribution, working with different styles |
| Leadership | Initiative, influencing others, accountability (no management title required) |
| Communication | Clarity, audience awareness, explaining difficult topics |
| Problem-solving | Analysis, creativity, structured thinking |
| Decision-making | Judgement, weighing trade-offs, acting under uncertainty |
| Working under pressure | Prioritisation, calm, meeting deadlines |
| Conflict / resilience | Handling disagreement, recovering from setbacks |
| Adaptability | Coping with change, learning quickly, adjusting plans |
Read the person specification. Highlight every competency listed. That list is your prep brief. Civil Service applications often tell you exactly which competency each question targets. Treat that as the answer key.
15 Common Competency Based Interview Questions
Employers rarely publish their exact question bank, but these fifteen come up constantly across UK graduate schemes, public sector roles, and corporate hiring. Prepare STAR stories for each theme, not word-for-word scripts.
- Tell me about a time you worked effectively in a team.
- Describe a situation where you showed leadership.
- Give an example of when you solved a difficult problem.
- Tell me about a time you handled conflict in the workplace.
- Describe working under pressure to meet a deadline.
- Give an example of when you had to communicate a difficult message.
- Tell me about your biggest professional achievement.
- Describe a time you failed and what you learned.
- Give an example of when you showed initiative.
- Tell me about a time you had to adapt to a significant change.
- Describe a situation where you influenced others without formal authority.
- Give an example of delivering excellent service to a customer or stakeholder.
- Tell me about a time you made a difficult decision.
- Describe a situation where you had to learn something quickly.
- Give an example of when you paid careful attention to detail.
Expect follow-ups on any of these. "What was your individual contribution?" "What would you do differently?" "What was the hardest part?" The initial question opens the door. The follow-ups decide your score.
For ten more questions with detailed guidance on what interviewers are really testing, see our behavioural interview questions guide.
How to Answer Competency Based Questions Using STAR
Every competency based interview answer should follow STAR: Situation, Task, Action, Result. Some UK employers add Reflection (STARR), which captures what you learned.
| Section | Share of answer | What to include |
|---|---|---|
| Situation | 10–15% | Brief context: where, when, what was at stake |
| Task | 10–15% | Your specific responsibility or challenge |
| Action | ~60% | What you did, step by step. Use "I", not "we" |
| Result | 15–20% | Specific outcome with a number, decision, or learning where possible |
Most weak answers are too much Situation and not enough Action. I've heard candidates spend 80% of their time on background and rush the result in one vague sentence: "and it went well." The interviewer cannot score that. If your STAR answer has a twelve-minute Situation, it is not STAR. It is a podcast.
A team context is fine. The interviewer still needs to hear your role. "We decided to restructure the project" tells them nothing. "I mapped the dependencies, proposed a phased rollout, and paired two engineers on the critical path" tells them everything.
Target length: 90 to 120 seconds per answer. Pause for one to two seconds before you start. It feels long to you. To the panel, it looks like you're thinking rather than buffering.
Three Example Competency Based Interview Answers
These are templates. Swap in your own stories. The structure is what matters.
1. "Give an example of a time you worked in a team"
Situation: "In my previous role, our team had six weeks to migrate a legacy reporting system before the old platform was decommissioned."
Task: "I was the analyst on the project, responsible for mapping existing reports to the new system and coordinating with two developers."
Action: "I audited all 40 existing reports, grouped them by priority with the product owner, and created a shared tracker so everyone could see blockers. When one developer fell behind, I picked up the documentation for their section and ran daily 15-minute stand-ups to keep us aligned."
Result: "We migrated all critical reports on time with zero downtime. The tracker approach was adopted by two other teams in the department."
2. "Tell me about a time you solved a difficult problem"
Situation: "Customer checkout conversion dropped 12% after a payment provider updated their authentication flow, two days before a major product launch."
Task: "As product owner, I needed to find the root cause and restore conversion before launch."
Action: "I pulled error logs, mapped the old and new authentication flows side by side, and identified three integration points that needed updating. I paired with an engineer to patch them and set up staging tests with real card types before we deployed."
Result: "Conversion returned to pre-update levels within 36 hours. We launched on schedule, and I documented the new flow so the team could handle future provider changes without a fire drill."
3. "Tell me about a time you failed"
Situation: "I was leading a client onboarding project and committed to a two-week timeline without checking our engineering capacity."
Task: "I needed to deliver the onboarding while managing the client's expectations when we slipped."
Action: "When I realised we would miss the deadline, I told the client immediately, explained the specific bottleneck, and proposed a phased delivery: core features in week two, remaining integrations in week four. I also built a capacity check into our sales handoff so we would not repeat the mistake."
Result: "The client stayed with us. The phased approach became our standard onboarding process, and we have not missed a committed deadline since."
How to Prepare for a Competency Based Interview
Preparation for competency based interview questions is mostly story selection and spoken rehearsal. Not highlighting your CV. Not reading advice articles silently and calling it done.
Step 1: Extract competencies from the job description
Copy every competency from the advert and person specification. If they use Civil Service language ("Delivering at Pace", "Making Effective Decisions"), learn those exact phrases. Your answers should mirror their vocabulary.
Step 2: Build a story bank of five to eight examples
Draw from the last two to three years of work, study, volunteering, or extracurricular activities. Map each story to two or three competencies.
| Story type | Competencies it covers |
|---|---|
| Led a project under a tight deadline | Leadership, pressure, teamwork, delivering results |
| Resolved a conflict with a colleague or stakeholder | Communication, conflict, influencing |
| Failed at something and changed your approach | Self-awareness, learning, resilience |
| Improved a process or solved a recurring problem | Problem-solving, initiative, customer focus |
| Influenced a decision without formal authority | Leadership, communication, stakeholder management |
Write STAR bullet points, not a script. Memorised scripts are brittle. The interviewer asks the same question in a slightly different way and your polished answer no longer fits.
Step 3: Practise out loud
Silent preparation is not preparation. Reading notes trains recognition, not retrieval. The first time your mouth forms the answer should not be in front of the panel.
Practise each story out loud. Time it. Aim for 90 to 120 seconds and a speaking pace of 120 to 160 words per minute. Instant Interview gives you a STAR score, filler word rate, and pace feedback after every answer, which beats guessing whether you rambled.
Step 4: Prepare for follow-ups and hypotheticals
Some competency interviews mix behavioural questions with hypothetical scenarios: "What would you do if a client wasn't happy with your work?" Try to anchor hypotheticals to a real past example where you can. "I faced something similar when…" is stronger than a purely imagined response.
Common Mistakes to Avoid
Giving hypotheticals instead of real examples. "I would usually handle conflict by…" is unscorable. If you haven't faced the exact situation, pick the closest real example and say so.
Rambling through irrelevant background. Use STAR to stay structured. If you're three minutes in and still setting the scene, stop and jump to Action.
Humblebrag failures. "My weakness is I care too much" or "I once worked too hard." Pick a genuine failure, own it, show what changed.
Using the same story for every question. One project can answer multiple competencies if you shift emphasis. Using it five times in one interview suggests you have nothing else.
Badmouthing former colleagues. Describe conflict professionally. Focus on the situation and your response, not how someone was impossible to work with.
Embellishing the truth. Panels can and do check references. Invented examples fall apart on follow-ups.
Can You Use the Same Example for Different Questions?
Yes, with caveats. A single project can demonstrate leadership, teamwork, problem-solving, and communication if you adapt the emphasis.
For a leadership question, highlight how you set direction and made decisions. For a teamwork question, emphasise collaboration and how you handled different working styles. For problem-solving, focus on analysis and the creative solution.
Do not reuse the same story for every question in the interview. Two or three times across a 45-minute panel is fine. Five times is not.
How Panels Score Your Answers
Most UK competency panels use a simple scoring scale. You won't see the sheet, but knowing how marking works helps you shape answers.
| Score | What the panel heard |
|---|---|
| Strong (4–5) | Specific example, clear personal actions, measurable result, directly addresses the competency asked |
| Adequate (2–3) | Real example but vague on individual contribution, or weak result |
| Weak (0–1) | Hypothetical, no example, or example does not match the competency |
I once saw a candidate give a strong teamwork story when the question was about leadership. Wrong competency. Same anecdote, wrong lens. They scored a 2 when they could have scored a 5 with a small shift in emphasis.
Feedback beats vibes. "I think that went okay" is not enough. You need to know where the answer lost structure or became hard to follow before you're in front of a real panel.
How Many Questions Should You Expect?
Most standard competency based interviews include three to six scored questions in a 45 to 60 minute session. Assessment centres may run more across multiple interviewers.
Have five to eight STAR examples ready. Some will be used. Some of your prepared questions will be partially answered during earlier conversation. Spares keep you from improvising under pressure.
If you're also facing skills-based interview components (practical exercises, case studies, role-plays), competency questions are usually just one part of the day. Do not assume one prep approach covers everything.
Adrian, Instant Interview
