The scoring sheet behind a behavioural interview

What a competency framework is, how interviewers mark against one, and how to work out which competencies a given job description is testing for.

The short answer: A behavioural interview in any large employer is scored against a competency framework: a written list of behaviours, each with a scale describing what a weak, adequate and strong answer looks like. The interviewer is filling in a form. That changes preparation considerably — instead of guessing what impresses, you can work out which four or five competencies a role is testing from the job description, and prepare evidence against each one. The tell is the language: "stakeholder management", "commercial awareness", "collaboration", "resilience" are not decoration in a posting, they are the mark sheet quoted back at you.

Key points

The interviewer is completing a scoring form, not forming a general impression — the scores are what survive into the hiring decision.
A job description usually names the competencies directly, which makes the mark sheet largely readable in advance.
Prepare one strong story per competency rather than many stories with no mapping; coverage beats volume.
Weak answers are usually generic rather than wrong — the scale rewards specificity, and a general statement scores at the bottom of it.

What is actually on the interviewer's desk

Structured interviewing exists because unstructured interviewing is a poor predictor and hard to defend. So large employers write down the behaviours the role needs, define what each looks like at several levels, and ask every candidate the same questions against them.

A typical scale for one competency — "influencing others"
Level	What it looks like in an answer
1 — limited	Describes what the team decided; own contribution unclear
2 — developing	States a position and who they told; no adaptation to the audience
3 — effective	Tailors the argument to the person, anticipates objections, follows up
4 — strong	All of the above, plus changes their own position where the counter-argument was better

Illustrative of the shape these scales take. The exact wording differs by employer; the structure rarely does.

Reading a scale like that changes what you prepare. Level 4 is not a more impressive story than level 3 — it is the same story with one extra element in it, and that element is something you can decide to include.

Reading the mark sheet out of the job description

Job descriptions are written by the same people who own the framework, and the vocabulary leaks. Abstract nouns that appear more than once are almost always competencies.

Copy the posting into a document and highlight every abstract behavioural noun.
Group the duplicates. Four or five distinct clusters usually remain.
Map one story from your evidence bank to each. Where two competencies map to the same story, find a second for one of them.
For each, check you can name a trade-off and a reflection — that is the gap between an adequate and a strong score.

This is also how you decide what to lead with. If "commercial awareness" appears three times, the interview will test whether you understand how the employer makes money, which is the first of the four research questions.

Where the marks are actually lost

Generic answers. "I always make sure to communicate clearly with stakeholders" describes a policy, not an event. Scales reward specific incidents; a policy scores at the bottom.
No trade-off. A story where the right answer was obvious evidences nothing about judgement. Choose the story where two reasonable options existed.
Unowned outcomes. Describing what happened without saying what you decided leaves the interviewer nothing to mark.
Repeating one story. Using the same project for four competencies signals a narrow base of experience, even when it is not true.
Running out of time. Frameworks have a fixed number of questions in a fixed slot. A four-minute answer costs you the last competency entirely, which is scored as a zero rather than as an omission.

One thing a framework changes about how you should answer: interviewers usually have to record evidence against each competency separately, so an answer that touches four of them lightly is harder to score than one that evidences a single competency thoroughly. If a question is clearly aimed at collaboration, answer it about collaboration. Volunteering that the project also demonstrated your commercial awareness and resilience does not earn those marks — those have their own questions — and it dilutes the evidence for the one being asked about.

It also explains a piece of interview behaviour that otherwise looks rude. When an interviewer interrupts to ask "and what did YOU do?", they are not being sceptical about your story; they are missing the evidence they need to write on the sheet. Treat every interruption as a request for a specific kind of detail rather than as a challenge, and answer the narrower question directly instead of returning to the narrative.

Frequently asked questions

How do I find out which competencies are being tested?

Read the job description for repeated abstract nouns — collaboration, judgement, client focus, resilience, commercial awareness. Those are usually lifted from the framework. Large employers, particularly in banking and consulting, also publish their values or competencies on the careers site, and graduate schemes almost always do. Four or five is typical for one interview.

What separates a strong answer from an adequate one?

On most scales it is specificity and ownership. An adequate answer describes a reasonable thing that happened; a strong one names the trade-off that was faced, the decision that was made, why it was made, and what it cost. The gap is rarely the quality of the underlying story — it is how much of the thinking behind it makes it into the answer.

What if I have no example for one of the competencies?

Use a smaller example rather than none. Frameworks score the behaviour, not the scale of the setting, and a well-told story about a two-person disagreement over a shared deliverable evidences collaboration as legitimately as a cross-department programme. An honest small example scores; "I have not been in that situation" does not.