Competency-Based Interview Questions and the Scoring Behind Them
In a competency interview the criteria are usually written down before you arrive, and often published. Most candidates never read them — which is the easiest advantage anyone has ever left on the table.
How Competency Scoring Actually Works
This format is standard in the public sector, large corporates, graduate schemes, and most regulated industries. It is far more mechanical than it looks.
Not a vague quality but a written definition with observable behaviours underneath it — for example, delivering at pace, or making effective decisions. Each has its own criteria.
Interviewers mark against that competency alone, usually on a scale of about one to seven or against level descriptors. A brilliant answer to the wrong competency scores nothing on the right one.
Scorers are trained to look for what you specifically did. Descriptions of what you believe, or what your team did, produce a low mark no matter how well they are delivered.
One weak answer usually cannot be rescued by a strong one elsewhere, because they are recorded separately. That is why every question needs its own prepared example.
Competency frameworks are frequently published — in the job pack, on the careers site, or in a civil service or NHS framework anyone can download. That document names the exact behaviours being scored and often gives the wording of each level. Reading it before you build your examples is the single highest-return hour of preparation available for this format.
Eight Steps That Match This Format
Competency interviews reward preparation more mechanically than any other format, because you can often see the mark scheme.
Check the job pack, the careers site, and any published sector framework. If you cannot find it, ask the recruiter which competencies will be assessed — a completely standard question.
Each with a different context, and each with numbers in it. You are aiming for coverage of the framework rather than for your ten favourite anecdotes.
Competencies down one side, stories across the top. Gaps in the grid are exactly where you will be caught, and they are visible in five minutes.
The same project can evidence leadership and problem-solving with a different emphasis. That flexibility is what saves you when the question is not the one you expected.
Situation and task in about fifteen seconds, action in ninety, result in fifteen. Most people invert this and spend two minutes on background.
Go through each story and replace we with I wherever it was actually you. Scorers cannot award marks for a team's actions, and this is the most common reason good answers score low.
Percentage, time saved, money, headcount, error rate. Unquantified results are treated as unverified, and quantified ones are what get quoted in the panel's notes.
Resilience, learning from mistakes, and handling setbacks are standard competencies. Candidates who only prepare successes are left improvising the hardest questions.
Eight Competencies and the Questions That Test Them
The wording changes between organisations. The underlying competencies barely change at all.
Teamwork — "Tell me about a time you worked with a difficult colleague."
Scorers want your specific behaviour towards that person, not a character study of them. Spend one clause on the difficulty and the rest on what you did: what you tried first, what you changed, what the working relationship looked like afterwards.
Leadership — "Describe a time you led without formal authority."
This exact framing is extremely common because it separates influence from job title. Show how you got people to agree, name the resistance you met, and be explicit about the decision you personally made.
Problem-solving — "Tell me about a complex problem you solved."
The score depends on your method being visible. How you diagnosed it, what you ruled out and why, what you chose. A story where the solution simply appears evidences luck rather than competence.
Delivering at pace — "Give an example of working to a tight deadline."
They are scoring prioritisation, not stamina. Say what you dropped or deferred and why that was the right call. Answers that amount to I worked all weekend score poorly in almost every framework.
Resilience — "Tell me about a significant setback."
Pick a real failure with a real cost. State what you got wrong without cushioning it, then what you changed, then evidence the change held — the second time this came up, here is what happened.
Communicating and influencing — "Describe a time you had to persuade someone."
Name the audience, what they cared about, and how you adapted the message. The strongest versions include the objection you had not anticipated and how you handled it in the moment.
Making effective decisions — "Tell me about a decision you made with incomplete information."
State what you did not know, how you bounded the risk, what you decided, and what happened. Include the trade-off you accepted — decisions with no cost attached read as invented.
Customer or service focus — "Give an example of going beyond what was expected."
Beware the story where you simply did more work. The higher-scoring version is where you identified an unstated need and changed something so it did not recur, with a measurable outcome.
Eight Techniques That Move the Score
Small, mechanical, and each one directly attached to how these answers are marked.
Saying this is an example of influencing without authority tells the scorer which box to fill. It sounds blunt and it demonstrably helps.
No marks are available for background. The action section is where the entire score lives and it is where most candidates run out of time.
We chose is unscoreable. If the decision was yours, say so; if it was not, describe the part that was. This alone separates mid from high marks.
Cut processing time from six days to two. Unquantified outcomes are recorded as unverified, and vague improvements do not get quoted in the panel debrief.
Under pressure people deliver the story they prepared rather than the one requested. On a scored sheet that is a zero on the intended competency.
What did you do when they pushed back means the scorer is missing evidence for a specific behaviour. Give the detail rather than restating the summary.
Panels notice, and a single example cannot evidence six competencies. This is exactly what the story grid prevents.
One sentence on what you took from it, especially for failure competencies. Many frameworks have reflection written into the criteria as an explicit behaviour.
Four Questions Worth Asking
This format is transparent by design, so you can ask about it directly without any awkwardness.
"Which competencies will I be assessed against?"
Entirely normal to ask before the interview, and recruiters routinely tell you. It converts guesswork into targeted preparation.
"Is there a published framework I should be reading?"
In the public sector and large corporates there usually is, and it often contains the exact level wording the panel scores against.
"How are these competencies used after hiring — in reviews, in promotion?"
Tells you whether the framework is a live management tool or a recruitment ritual, which says a lot about the organisation.
"Which of these competencies matters most in the first year?"
The answer describes the real job, and it is a useful question to leave the panel thinking about.
"This is an example of influencing without authority. Our two teams were duplicating a monthly reconciliation and neither manager owned it. I pulled the two process owners into one session, mapped both versions on a whiteboard, and showed that seventy percent of the steps were identical. I proposed one team run it and the other consume the output, and I took on writing the handover myself so neither side inherited extra work. It went live the next cycle and cut about eleven hours a month across the two teams. What I learned was to bring a drafted proposal rather than an open question — people agree far faster to something concrete."
Six Ways Competency Answers Lose Marks
The most common and most expensive error in this format. Scorers can only credit your own actions, so make yours unmistakable.
Situation and task are worth almost nothing. Fifteen seconds of context, then straight into what you did.
Unquantified outcomes are treated as unverified. Attach a figure to every story in your bank before the interview.
Panels notice immediately, and it leaves whole competencies with no evidence. Build the grid and fill the gaps.
A great teamwork story scores zero on a decision-making question. Listen for which competency is being asked and pick accordingly.
Resilience questions need a real setback with a real cost. A failure that turned out fine on its own evidences nothing.