Competency-based interviewing: a practical guide

Competency-based interviewing is one of those terms that sounds like corporate jargon but actually describes a genuinely useful discipline: deciding, before you meet anyone, exactly which capabilities the role requires, and then interviewing for evidence of those specific capabilities rather than for a general good impression. It's the difference between leaving an interview saying “I liked them” and saying “they demonstrated strong evidence on three of the four things this job needs.”

It's best understood as a focused, practical form of the structured interview — same backbone of consistent questions and rubric scoring, organized specifically around defined competencies. This guide covers how to choose those competencies, turn them into questions, score the answers, and sidestep the traps that turn a competency framework into box-ticking.

Define the competencies

The foundation — and the step most often rushed — is choosing the right competencies. A competency is a specific, observable capability the role genuinely depends on: not “leadership” in the abstract, but “can align a team around a decision they initially disagreed with.” Aim for four to six; more than that and the interview becomes a shallow tour, fewer and you miss something that matters. Derive them from the actual work, the same way you'd build a skills-based job description — the two should describe the same role.

The discipline here is resisting the urge to list traits you admire (“passionate,” “driven”) and instead naming behaviors you could actually observe evidence of. If you can't imagine what a concrete example of a competency would sound like, it's too vague to interview for.

Write the questions

With competencies fixed, the questions almost write themselves: for each one, ask for a real past example. Behavioral phrasing — “tell me about a time you…” — works because past behavior predicts future behavior far better than hypotheticals, which mostly test imagination and confidence. One or two strong questions per competency is plenty; the depth comes from follow-ups that probe what the candidate actually did, not what “the team” did.

Ask the same core questions of every candidate so you're comparing like with like. This consistency is what turns a set of pleasant conversations into a comparable evaluation — and it's exactly where unstructured interviewing falls down.

Score against a rubric

A competency interview without a rubric collapses back into impressions. For each competency, write down in advance what a weak, solid and strong answer contains, then score each candidate's response independently — ideally before any group discussion, so the loudest voice in the debrief can't anchor everyone else. The rubric is what makes the method fair and defensible: everyone is held to the same explicit standard, set before anyone walked in the room.

The common traps

Two failure modes recur. The first is the competency framework that's so generic it applies to every role — “communication, teamwork, problem-solving” — which gives the comfort of structure without the substance; tie competencies to the specific job or they measure nothing. The second is treating the interview as a checklist to tick rather than evidence to weigh: a candidate can mention all the right keywords without demonstrating any real capability, which is why scoring the depth and specifics of examples matters more than spotting buzzwords.

How Spoon does it

Spoon runs competency-style structured interviews automatically: the role's required skills drive a consistent AI interview that asks for real examples, explores them with follow-ups, and scores the substance against the role — the same for every candidate, surfaced as an anonymized, merit-ranked shortlist. The competency framework you'd otherwise build and police by hand is simply how it works. See how it works.

Frequently asked

Keep reading