Competency-Based Interview Questions: Scored Against a Rubric You Can Predict

Competency based interview questions ask you to describe something you have actually done, and the interviewer scores your answer against a written list of behaviours. That list usually exists as a document — a competency framework — and in many organisations you can read it, or infer it accurately, before you walk in.

That makes this the most predictable interview format there is. Most candidates still wing it, tell a warm story, and lose marks on things they never knew were being counted.

What a competency framework actually is

A competency framework is the organisation's written definition of good behaviour at work — usually 5 to 12 named competencies, each with "behavioural indicators" describing what a strong and a weak example look like. The interviewer is not judging vibes. They are ticking indicators on a form and putting a number in a box.

That form is why competency interviews feel oddly rigid: fixed questions, everyone asked the same thing, the panel scribbling instead of chatting. It's not coldness. It's an audit trail — the format exists so the decision can be defended later.

Where to find the framework:

• The job ad's "essential criteria" — these are often the competencies, copied straight across
• The organisation's values or careers page, which frequently names the same behaviours
• Published public-sector frameworks — many governments, health services and universities publish theirs openly, which is a gift
• The recruiter, who will usually tell you the competency areas if you ask directly

Practice varies. Some employers score every answer 0–4 against indicators; smaller firms run a looser version. Ask which one you're in.

The competencies that keep coming back

Most frameworks are variations on the same six or seven themes, whatever they're called locally. Learn the theme and you'll recognise the question stem instantly, even in unfamiliar wording.

Competency	Typical question stem	What the scorer is ticking
Working with others	"Tell me about a time you worked with a difficult colleague."	You named the friction, adapted your approach, kept the relationship intact
Delivering at pace	"Describe a time you had to hit a tight deadline."	You prioritised deliberately, cut something, and delivered
Decision-making	"When did you make a decision with incomplete information?"	You weighed options, chose, and owned the outcome
Communicating	"Give an example of explaining something complex to a non-expert."	You adjusted to the audience and checked understanding
Resilience	"Tell me about a setback and how you handled it."	You stayed functional, learned something specific, applied it
Leadership	"Describe a time you influenced people without authority."	You set direction, motivated, took responsibility for results

Two rules for reading the table. First, the middle column is the disguise and the right column is the exam — answer the right column. Second, the same story can serve several rows depending on which part you foreground.

Why STAR genuinely matters here (not just as advice)

STAR — Situation, Task, Action, Result — is the correct structure for competency based interview questions because the scoring form has roughly those boxes. If your answer buries the Action, the scorer has nothing to tick, and unticked means unscored.

This is the honest case for STAR that most articles never make. It isn't a stylistic preference. It's format-matching:

• Situation and Task should be fast — two or three sentences, just enough for the stakes to land
• Action is where the marks live and should be over half your answer
• Result must be concrete and, where you can, quantified honestly

A useful test: could someone reconstruct your S, T, A and R from a transcript without guessing? If not, tighten it. Our STAR method examples walk through what that looks like in full sentences, and the broader patterns sit in our guide to behavioral interview questions.

The "we" problem that quietly costs you points

The single most common failure in competency interviews is describing what the team did instead of what you did. The rubric scores an individual. Every "we decided" is a sentence that cannot be attributed to you.

It usually comes from good instincts — modesty, team loyalty, discomfort with self-promotion. Doesn't matter. The scorer cannot award marks to a pronoun.

The fix is small and mechanical:

• Set the scene in "we", then switch to "I" the moment you reach your actions
• Name your specific decision, message, calculation or conversation
• Say what you did when it was hard, not just what the plan was
• If credit is genuinely shared, be exact: "the team ran the migration; I owned the rollback plan"

Being precise about your own contribution is not arrogance. It's the answer to the question they asked.

How many examples to prepare

Prepare five or six flexible stories, not one per competency. A good story has enough moving parts to be angled several ways — the deadline story is also a prioritisation story, a communication story and possibly a resilience story.

Building one example per competency creates two problems: you memorise twelve brittle scripts, and you freeze when a question doesn't match any of them. A small, well-known set survives surprise questions much better.

Choose stories that:

• Are recent enough to remember in detail under pressure
• Involve a real obstacle — no obstacle means no Action to score
• Have an outcome you can state plainly, including the ones that went sideways but taught you something
• Come from different contexts, so you're not answering everything with the same project

Then rehearse the joins, not the words: how you'd open the same story for "decision-making" versus "resilience". Rehearsed sentences sound rehearsed; rehearsed structure sounds fluent.

Turning your material into scored answers

Draft your stories, then interrogate them against the framework. The highest-value prep is not writing more — it's checking each answer for a clear Action and a clear Result, then cutting the setup in half.

AI is useful here as a sparring partner, not a scriptwriter. Paste the published competency and your draft, and ask which indicators are evidenced and which are missing — it's good at spotting the gap, bad at inventing your experience. Anything it adds that you didn't do will collapse under a follow-up question.

Warm up on the two questions that open most interviews: our guides to Tell me about yourself and the wider interview questions hub cover what comes before the competency block starts.

Frequently asked questions

Are competency based interview questions the same as behavioural questions?

Nearly. Both ask for past examples, but a competency interview explicitly maps questions to a named framework and scores them against indicators. In practice, prepare the same way and treat every behavioural question as if it's being scored.

Can I use the same example for two different competencies?

Yes, and interviewers expect it — but re-angle it. Foreground the decision if they're scoring decision-making, the difficult conversation if they're scoring working with others. Repeating the identical answer verbatim is what looks thin.

What if I have no example for a competency?

Use an adjacent one and be transparent about the gap. A smaller-scale, volunteer or academic example scores far better than a vague hypothetical, because hypotheticals contain no evidence of behaviour at all.

How long should each answer be?

Around two minutes is the usual sweet spot, with most of it spent on your actions. If the panel is silent and writing, keep going; if they interrupt to probe, that's a good sign — they're chasing detail to award marks.

Competency based interview questions reward the candidate who understands the machinery: find the framework, learn the indicators, build five or six flexible stories, and make your own actions impossible to miss. That's not gaming the system — it's answering the question they actually asked.

If you want that turned into a working process — positioning, examples, prompts and rehearsal in order — Land the Offer with AI lays it out step by step, with one rule: everything you say has to survive the follow-up question.