HIIRD/Interview guides/Competency-based

The competency interview: claims need evidence.

A competency interview is an audit. The job needs specific capabilities, and the interviewer walks through them one by one asking you to prove each with your own history.

Why employers use competencies

A competency is a skill or behavior the employer has decided the job needs, written down in advance. Big employers, public sector bodies, and graduate programs often keep a formal list, called a competency framework, and build every interview question from it.

The UK civil service is a well-known example. Since 2019 it has hired using Success Profiles, which replaced its older competency framework. Each job ad usually names four or five behaviors, like Working Together or Delivering at Pace, and candidates are sifted and interviewed against exactly those. Many US employers do the same thing with different labels.

Why it matters to you: the scoring guide is usually hiding in plain sight, in the job posting.

How it differs from behavioral

Behavioral questions ask about situations. Competency questions ask about capabilities: "Give me an example that demonstrates your ability to work under pressure." The skill is named in the question, and your answer is judged on whether it proves that exact skill, not whether it is a good story in general.

This is the format where a genuinely impressive story can score poorly, because it proved the wrong competency. If you have not read it yet, the behavioral interview guide covers the story structure both formats share.

Find the competencies before the interview

Read the job posting slowly, with a pen. Competencies show up in three places:

• A labeled list, like "Essential criteria," "Key competencies," or "Behaviors."
• The requirements section, hiding as adjectives: "detail-oriented," "excellent communicator," "comfortable with ambiguity."
• The duties section, hiding as verbs: "coordinate," "resolve," "analyze," "train." Each verb is a skill they will want proof of.

Write down the five to eight that appear most often or most prominently. That is your exam syllabus. Common ones for entry-level roles: communication, teamwork, problem solving, attention to detail, adaptability, customer focus, planning and organizing, and working under pressure.

The structure interviewers reward: claim, evidence, impact

Name the competency in your own words, give a concrete example that shows it, and connect it to what changed. Saying "yes, I am organized" is a claim. A claim with no evidence scores near zero in this format, no matter how confidently it is delivered.

Use their words. If the posting says "managing a quality service," say "quality service" when you name the competency. It makes it easy for the interviewer to tick the right box.

Two worked examples

Notice the shape: the claim defined ("the team does not feel my stress"), a specific incident, personal actions, and two outcomes. The competency named in the question is the spine of the whole answer.

Same shape, no full-time job required. The claim is defined in the first sentence, the evidence is specific and countable, and the impact is on real people.

Map one story to each competency

Take your list from the job posting and assign one story to each competency. Use a different story for each one if you can. A single strong project used for every answer starts to look like the only thing you have ever done.

For each story, write three lines: the claim in your own words, the evidence in one or two sentences, and the result. If a competency has no story yet, find one now, not in the interview.

How the questions are worded

Competency questions follow a few patterns. Once you hear the pattern, you know which skill is being tested:

• "Give me an example that demonstrates your ability to..."
• "Tell me about a time you used your [skill] to..."
• "Describe a situation where you showed..."
• "What evidence can you give me that you are..."

Expect probing follow-ups too: "What was your role, exactly?" "What would you do differently?" They are checking that the evidence is yours.

The mistakes that cost offers

• Proving a different competency than the one asked. Strong story, wrong exhibit.
• Evidence without impact. What resulted from your organized, calm, or decisive behavior?
• One example stretched across every question. Interviewers notice the third appearance of the same project.
• Talking about the skill in the abstract instead of showing it in an event.
• Ignoring the job posting. It usually tells you exactly which competencies will be scored.

How to practice

Turn each competency on your list into a question using the patterns above, then answer each one out loud. Time yourself and aim for 60 to 90 seconds. After each answer, ask one blunt question: if the interviewer only heard this, would they write down the skill they asked about? If not, move the claim to the first sentence and cut the setup.

Sources

• Global Government Forum, A guide to Success Profiles: what job applicants need to know.
• US Office of Personnel Management, Structured Interviews.