Competency-Based Interview Questions: How to Answer Them (With Real Examples)

TL;DR: Competency-based interview questions ask you to prove specific skills — teamwork, leadership, problem-solving — using real past examples, scored against a fixed rubric the interviewer won't show you. They're standard for UK civil service, NHS, graduate schemes, and most large multinationals. Answer with STAR, prepare one story per listed competency, and match your language to the job description's exact wording.

If the job ad lists "competencies" or the invite says "competency-based interview," you're not walking into a casual chat. You're walking into a scored assessment where the interviewer has a printed rubric in front of them, a list of required competencies from the job description, and a checkbox next to each one for "evidenced," "partially evidenced," or "not evidenced." Roughly a third to half of UK employers run interviews this way, and the format has spread well beyond the UK — into NHS trusts, EU institutions, Singapore statutory boards, and graduate programs at multinationals worldwide.

Most prep guides hand you a list of 50 questions and a STAR method reminder, then leave you to figure out the rest. This one covers what's actually different about competency-based interviews, the competencies employers test most, and how to build answers that survive a rubric — not just a friendly interviewer's gut feeling.

---

What Is a Competency-Based Interview?

A competency-based interview evaluates you against a predefined list of skills — called "competencies" — that the employer has already decided matter for the role. Each competency (say, "Teamwork" or "Delivering at Pace") has a written definition and a set of behavioral indicators the interviewer is trained to listen for.

The UK Civil Service's Success Profiles framework is the clearest public example: nine core Behaviours, each with grade-specific examples of what "good" looks like, used across every government hiring process. If you've ever seen a UK job ad list behaviours like "Communicating and Influencing" or "Making Effective Decisions" with a note to "provide evidence," that's Success Profiles in action — and it's the same underlying logic multinationals, NHS trusts, and graduate schemes borrow, even when they don't use the UK's exact terminology.

The practical difference from a normal interview: your answer isn't judged on whether it sounds impressive. It's judged on whether it contains the specific behavioral evidence the rubric is looking for. Ramble through a great story without naming what you decided and did, and you can still score "not evidenced."

---

Behavioral vs. Competency-Based Interview: What's the Actual Difference?

People use these terms interchangeably, and in casual conversation that's mostly fine — competency-based interviews use behavioral questions. But there's a real distinction worth knowing:

• Behavioral interviews ask about the past broadly ("Tell me about a time you dealt with conflict") and the interviewer evaluates your answer somewhat subjectively, often without a formal scoring sheet.
• Competency-based interviews map each question to a named, pre-published competency with a written rubric, and the interviewer scores you against defined levels — not vibes.
• Situational interviews are the odd one out: they ask hypothetical future questions ("What would you do if...") instead of real past examples. That's a different skill from what this guide covers — see our situational interview questions guide if that's the format you're facing — don't mix the two prep strategies, since a hypothetical answer in a competency-based interview can score zero.

In practice: assume any interview labeled "competency-based" is behavioral-question format with a formal scoring rubric behind it. That rubric is why generic, unstructured stories underperform here even when they'd land fine in an informal interview.

---

The Core Competencies Employers Actually Score You On

Job ads rarely reuse the exact same list, but most competency frameworks — including SHRM's competency-based interview question bank — cluster around the same handful of core competencies interview examples draw from repeatedly:

• Communication — explaining complex information clearly, adjusting to audience
• Teamwork / Collaborating — working with others, especially across friction
• Leadership — influencing outcomes without always having formal authority
• Problem-solving / Analysis — breaking down ambiguous or messy situations
• Decision-making — choosing under incomplete information or time pressure
• Resilience / Managing pressure — staying effective when things go wrong
• Delivering results — hitting a goal despite obstacles, on a deadline
• Managing change — adapting to shifting priorities or new processes
• Customer focus — prioritizing the needs of the person you serve

Read the job description before the interview and highlight every competency word it uses — "collaborative," "resilient," "influence," "deliver." That's your rubric leaking through the ad. Prepare at least one story per listed competency, not one generic story you try to stretch across all of them.

---

How to Answer With the STAR Method (and Why It Matters More Here)

STAR — Situation, Task, Action, Result — isn't optional in a competency-based interview the way it might be in a casual one. It's the structure the rubric is built to detect. Interviewers trained on Success Profiles-style frameworks are explicitly listening for each STAR component because that's how they map your answer to "evidenced."

The part most candidates get wrong: Action is where the score comes from. If your story keeps saying "we decided" and "the team did," the interviewer often can't credit you individually — literally can't tick the box, because the competency is about your behavior, not your team's. Say "I proposed," "I decided," "I pushed back." Save "we" for describing outcomes, not decisions.

Keep the shape tight: 10–15 seconds of Situation and Task, 30–45 seconds of Action, 15–20 seconds of Result. If you're two minutes into Situation and haven't said "I" once, you've lost the thread the rubric is tracking.

This is also where a tool like AceRound earns its keep during the actual interview — it listens in real time and can nudge you toward the STAR structure or flag when your answer is drifting into "we" language instead of "I" language, especially useful if nerves make you blank on a competency you didn't prep for. It won't invent your work history for you — you still need real stories — but it helps you deliver the ones you have in the shape the rubric wants.

---

12 Competency-Based Interview Questions and Answer Examples

These are competency based interview questions and answers examples grouped by the competency they're testing, with what each is really checking for and a short fragment showing the shape of a strong Action beat.

Teamwork "Tell me about a time you worked with a team member who had a very different working style to yours." Testing: whether you adapt without losing effectiveness. Strong Action fragment: "I asked her how she preferred status updates — turned out she wanted async written summaries, not stand-ups — so I switched formats just for our thread."

Leadership "Describe a situation where you had to motivate a team without formal authority." Testing: influence, not title. Strong Action fragment: "I mapped out what mattered to each person individually and tied the deadline to their specific interest, rather than sending one generic push."

Problem-solving "Give an example of a complex problem you had to break down." Testing: structured thinking under ambiguity. Strong Action fragment: "I split the issue into three testable hypotheses and ruled out two within a day instead of guessing."

Decision-making "Tell me about a decision you made with incomplete information." Testing: judgment under uncertainty, not perfect hindsight.

Resilience "Describe a time something you were responsible for went badly wrong." Testing: self-awareness and recovery, not a spotless record. Never claim nothing has gone wrong — that reads as low self-awareness, not competence.

Delivering results "Tell me about a time you hit a deadline despite a major obstacle." Testing: follow-through under pressure.

Managing change "Describe a time your priorities shifted suddenly and how you handled it." Testing: adaptability without dropping quality.

Communication "Tell me about a time you had to explain something technical to a non-technical audience." Testing: clarity, empathy for the listener.

Customer focus "Give an example of going beyond what was expected for a customer or stakeholder." Testing: service orientation, judgment on where to invest extra effort.

Conflict management "Tell me about a disagreement with a colleague and how it was resolved." Testing: whether you can disagree productively, not avoid conflict entirely.

Planning and organizing "Describe how you managed multiple competing deadlines." Testing: prioritization method, not just busyness.

Innovation "Tell me about a time you improved a process that wasn't broken, just inefficient." Testing: initiative beyond your assigned scope.

For every question above, the rubric-relevant part is the Action — name the specific choice you made, not the situation you were dropped into.

---

UK Competency-Based Interviews: What's Actually Different

If you're interviewing in the UK — civil service, NHS, local government, or a large UK-headquartered company — expect the format to be more explicit than almost anywhere else. Success Profiles interviews often tell you the exact Behaviour titles in advance ("Working Together," "Communicating and Influencing," "Delivering at Pace"), sometimes even the specific indicators for your grade level, published on gov.uk before you walk in.

Two things that trip up candidates new to UK competency-based interviews:

1. Grade-specific bar. The same Behaviour is scored differently at different seniority levels. "Leadership" for an entry-level role means something narrower than for a senior manager — check the grade-specific indicators, not just the Behaviour name.
2. Strict evidence-only rule. Assessors are trained to disregard hypothetical or "would-be" answers entirely, even mid-answer. If you drift into "I would probably..." partway through, expect a direct redirect: "Can you tell me about a time this actually happened?"

Outside the UK, the same evidence-only discipline applies even where the "Success Profiles" branding doesn't — Ireland's Public Appointments Service, Singapore's public sector, and most EU institution interviews run on near-identical logic.

---

Common Mistakes That Tank Competency-Based Answers

• Vague ownership. "We improved the process" tells the assessor nothing about you specifically.
• Wrong competency, right story. Reusing your best story for every question even when it doesn't actually demonstrate the competency being asked about. Assessors notice.
• No result stated. Ending on Action and never confirming what happened. Always close the loop, ideally with a number.
• Hypothetical drift. Sliding into "I would" instead of "I did." In an evidence-only format, this can zero out the answer entirely.
• One story, five interviews. Reusing the exact same anecdote for every competency because it's the only one you prepared. Interviewers on panels compare notes, and it reads as thin experience even when it isn't.

---

FAQ

What is a competency-based interview? An interview where questions map to a predefined list of skills (competencies), each scored against a written rubric based on real past examples — not hypothetical answers or general impressions.

How do you answer competency-based interview questions? Use the STAR method, lead with what you specifically decided and did (not "we"), state a concrete result, and match your competency stories to the exact list published in the job description or invite.

What's the difference between behavioral and competency-based interviews? Behavioral interviews ask about the past generally; competency-based interviews do the same but score each answer against a named, pre-published competency with defined levels — the format is stricter and more structured.

What is the STAR method? Situation, Task, Action, Result — a structure for answering "tell me about a time" questions that keeps your answer concrete and scorable, with the Action section carrying the most weight.

How many STAR examples should I prepare in advance? Enough to cover every competency listed in the job description or invite — typically 6–10 stories, since one strong story can often be angled to cover more than one competency if you emphasize different parts of it.

How do I prepare for a competency-based interview? List every competency word in the job ad, write one STAR story per competency, practice saying it out loud in under 90 seconds, and drop any sentence that starts with "we" when it should start with "I."

---

Prepping for a competency-based interview elsewhere in your job search? Our guides on the STAR method and behavioral interview questions go deeper on story structure and building a reusable story bank.

---

Author · Alex Chen. Career consultant and former tech recruiter. Spent 5 years on the hiring side before switching to help candidates instead. Writes about real interview dynamics, not textbook advice.