Competency-Based Interview Questions
A competency interview is not a conversation with a score attached. Each behaviour is marked on its own, from the evidence you actually state, and polish does not substitute for it.
A competency-based interview, sometimes called a structured or behavioural interview, asks you to describe past situations as evidence against a defined list of behaviours. The list is the point. Employers use it to score candidates consistently across many interviewers, which is also why the questions feel formulaic: they are deliberately standardised.
The frameworks differ by sector and country. UK government and public bodies use the Civil Service Success Profiles behaviours, with questions tied to named behaviours such as making effective decisions or communicating and influencing. Large professional services firms tend to publish a shorter values list. Technical graduate schemes frequently score engineering rigour, meaning testing, code review, security and data handling, as a competency in its own right rather than folding it into teamwork.
Understanding how the marking works changes how you answer. CogniPrep marks recorded practice sessions the same way real schemes do: each competency is scored independently against positive and negative indicators, only evidence you actually state counts rather than the impression you leave, and evidence that directly contradicts a behaviour caps that score low regardless of how fluent the rest of the answer was.
How the scoring actually works
Each behaviour is scored separately
Strong teamwork evidence does not lift your decision-making mark. Interviewers fill in a grid, so an answer that only ever demonstrates one behaviour leaves the other boxes empty even when it is the best story you have.
Only stated evidence counts
Assessors are trained to mark what you said, not what they inferred. Being personable is not evidence of collaboration. If you did not say what you did, it does not exist for scoring purposes.
Positive and negative indicators
Every behaviour has both. Under decision-making, using data is positive and deciding without checking the obvious source is negative. Both can appear in the same answer, and both are recorded.
Red flags cap rather than deduct
Evidence that contradicts a behaviour, such as blaming a colleague under teamwork or brushing past a rule under integrity, pins that competency low instead of losing a point. This non-linearity is why one throwaway line can sink an otherwise good interview.
Recency and specificity
Recent, detailed examples are easier to credit than distant, general ones. A vivid story from three months ago usually scores higher than a vague one from three years ago, even if the older achievement was bigger.
Follow-up questions are part of the mark
Probing questions exist to test whether the evidence is yours. Expect "what exactly did you do", "why that option", "what did the others think". Answers that thin out under probing are marked down accordingly.
Typical questions, behaviour by behaviour
Making effective decisions: tell me about a decision you made with incomplete information.
Credit comes from the method: what you knew, what you assumed, what you did to reduce the risk, and how you would have known if you were wrong.
Communicating and influencing: describe a time you explained something complex to a non-specialist.
Show the adaptation. What did you cut, what analogy did you use, and how did you check they had understood?
Working together: tell me about a time a team member was not pulling their weight.
The behaviour is inclusion and constructive handling. Escalating first, or working around the person silently, both trigger negative indicators.
Delivering at pace: give an example of hitting a difficult deadline.
Assessors look for planning and trade-offs, not heroics. Say what you dropped or renegotiated and who you told.
Integrity: describe a time you saw something that was not right.
Say what you did, who you told, and how quickly. Rationalising the shortcut is the classic red flag on this behaviour.
Engineering rigour: tell me about a time your change broke something.
Technical schemes score honesty here. Detection, rollback, root cause and the test or review step you added afterwards are what earn the mark.
Analytical rigour: describe a time your analysis was challenged.
Show the checks you had run, how you responded to the challenge, and whether you changed your conclusion when the evidence justified it.
Resilience: tell me about a setback and what you did next.
Evidence is the concrete action after the setback. Feeling motivated again is not scorable; what you changed is.
Preparing for a competency interview
- 1
Get the actual framework
Check the careers site, the job advert and the invitation email. Public sector roles usually name the behaviours outright and sometimes list the exact ones the interview will cover. Preparing against the published list beats preparing against a generic one by a wide margin.
- 2
Build a story-to-behaviour grid
Behaviours across the top, your stories down the side, a tick where a story gives real evidence. Empty columns are your preparation list. This takes half an hour and is the single highest-value thing you can do.
- 3
Put the action in the middle sixty percent
Situation and task are context and should be quick. The action section is where every indicator lives, so it should be the longest part of the answer by some distance.
- 4
Rehearse the probe, not just the story
For each story, answer three follow-ups out loud: what exactly did you do, why that option, what would you do differently. Interviewers get their evidence from the probes more often than from the first answer.
- 5
Audit your stories for red flags
Read each one back and look for the lines that contradict a behaviour: blame, rule-bending framed as initiative, deciding alone when consultation was obvious. Rephrase around what you actually did well rather than removing the difficulty.
- 6
Practise under recording conditions
Many schemes run the competency interview as a one-way video. Rehearsing to a camera is a different skill from rehearsing across a table, and it is the version that catches you out on the day.
Mistakes that cost marks
Answering in the present tense
"I always make sure the team is included" is a claim, not evidence. Competency questions want one dated event with a beginning and an end.
Hiding the individual in the team
Under working together, candidates over-correct into "we" and end with no personal evidence at all. Name the team once, then talk about your own contribution.
Spending the answer on the situation
Three minutes of background and fifteen seconds of action scores as a weak answer no matter how interesting the situation was. Indicators only appear in the action and result.
One red-flag sentence
A throwaway line about a colleague being useless or a process being pointless can cap that behaviour low on its own. It is the most avoidable way to lose a competency.
Reusing a story across behaviours
The same project can legitimately serve two behaviours, but using it for four makes the evidence base look thin and invites tougher probing.
Treating a values interview as a competency one
Some employers run a strengths or values interview instead, and a rigid STAR answer there reads as rehearsed. Check which style the invitation describes before you prepare.
Practise this before the real one
Record five behavioural questions to camera, with a prep window and a sector focus, then get AI feedback on clarity, structure and confidence.
Frequently asked questions
How is a competency interview different from a normal interview?
The questions are fixed in advance, tied to named behaviours, and scored against indicators by every interviewer in the same way. That structure is what makes preparation effective: you are not guessing a personality, you are supplying evidence against a published list.
What are the Civil Service Success Profiles?
The UK Civil Service assessment framework. It covers behaviours, strengths, ability, experience and technical elements, and recruitment adverts state which behaviours a role is recruiting against. If you are applying to a UK government department or public body, those named behaviours are your preparation list.
Does STAR still work?
Yes, as a shape for the evidence rather than a script. The version that scores well weights the action heavily and always ends with a result. Adding a short reflection turns it into STARL and usually picks up the learning indicator.
How long should a competency answer be?
About two minutes, then stop and let the interviewer probe. Candidates who talk for four minutes pre-empt the follow-up questions and lose the chance to add evidence where the interviewer actually wants it.
What if my example did not succeed?
An unsuccessful outcome handled well can score higher than a success you barely touched. State what happened, the judgement you exercised, and what you changed. Assessors are scoring behaviour, not luck.
Can I practise competency answers with feedback?
Yes. CogniPrep mock interview sessions can be focused on your sector, and the feedback scores your recorded answers against that sector’s competencies, in the style real assessors mark: engineering rigour and technical judgement for engineering, commercial awareness and integrity for finance, behaviour-anchored marking for public sector.
Practise this next
Practise with sector marking
Record five answers and get them scored against the competencies your sector’s assessors use.
Strengths-based interviews
The other style, and why a rehearsed STAR answer is the wrong shape for it.
Situational judgement tests
The same competency frameworks, tested as a multiple-choice sift earlier in the process.