Extended definition
Competency-based interviewing is the architecture that holds structured interviewing together. Without defined competencies, structured questions are arbitrary; with them, every question maps to a thing the role actually needs.
Competencies typically come from a competency framework — the company-wide list of capabilities by function and level. Each role’s interview kit selects 3-6 competencies most critical for that role, and the interview loop is designed so each interviewer covers specific competencies rather than overlapping.
Competency-based interviewing is the standard at most large enterprises and is increasingly common at scale-ups that want defensible, consistent hiring across functions.
How competency-based interviews work
A competency-based interview has four operating principles:
- Competencies are defined before the interview — The role’s hiring manager and recruiter agree which 3-6 competencies matter most. For an engineering manager, that might be technical depth, people leadership, cross-functional collaboration, and product judgment. For a senior salesperson, it might be discovery, deal management, objection handling, and territory planning.
- Each competency has dedicated questions — Behavioural and situational questions test each competency directly. A competency without questions doesn’t get measured.
- Interviewers own specific competencies — In a 4-5 person loop, each interviewer covers 1-2 competencies in depth rather than skimming all of them. This produces deep evidence on each competency from someone calibrated to assess it.
- Scoring rolls up to a competency view — Rather than a single overall score, the candidate is scored on each competency. The hiring decision considers strengths and gaps competency-by-competency, not a vague “they were strong overall.”
The competencies themselves come from a competency framework — ideally an organisation-wide one tied to the role architecture. Without that framework, competency-based interviewing devolves into ad-hoc lists per role. With it, competencies stay consistent across teams and over time, making cross-role comparison and internal mobility easier.
Why competency-based interviews matter
Competency-based interviewing forces the question “what does this role actually need?” before the first interview. That clarity is where most hiring goes wrong — interviews assess vague impressions of “fit” because nobody defined what fit means for this specific role.
Competencies make the requirements explicit and testable. The result is interviews that produce evidence aligned to job needs, hiring decisions defensible against challenge, and a calibration baseline that compounds over time.
For VPs of TA building hiring infrastructure, the competency layer is what allows everything else — interview kits, scorecards, calibration, performance prediction — to function.
Common mistakes and misconceptions about competency-based interviews
- Selecting too many competencies — Trying to assess 10 competencies in a single loop produces shallow evidence on all of them. Three to six is the sweet spot.
- Selecting the same competencies for every role — A senior IC and a manager need different competencies. Templates that don’t differentiate produce generic interviews.
- Confusing competencies with skills — Skills are narrow (“Python,” “salesforce administration”). Competencies are broader and more behavioural (“technical depth,” “customer focus”). Both matter, but the interview tends to assess competencies; skills are tested elsewhere.
- Letting interviewers freelance on competencies — If two interviewers both assess “leadership” without coordination, one tests strategic thinking and the other tests team management. Defining sub-areas per interviewer prevents this.
- Skipping the competency framework — Picking competencies fresh per role without an organisation-wide framework produces inconsistency over time. The framework is the foundation.
Frequently asked questions
What is a competency-based interview?
A competency-based interview assesses candidates against a defined set of competencies — the skills, behaviours, and capabilities required for the role — using questions and scoring designed to test each competency directly. Without defined competencies, structured questions are arbitrary; with them, every question maps to a thing the role actually needs.
How many competencies should a competency-based interview assess?
Three to six per role, allocated across the interview loop. Trying to assess more produces shallow evidence on each competency. Fewer than three risks missing important capabilities. The right number depends on role complexity and interview loop length.
What's the difference between a competency-based and a behavioural interview?
Competency-based interviewing is the architecture — defining what to assess. Behavioural interviewing is one technique used within it — asking past-tense questions to gather evidence. Most competency-based interviews use behavioural questions, but the categories aren't the same thing.
Where do competencies come from?
Ideally from an organisation-wide competency framework that defines capabilities by function and level. Without a framework, competencies get reinvented per role and consistency suffers. Building or buying a competency framework is usually a precondition for mature competency-based interviewing.
Can competency-based interviewing assess culture fit?
It can assess culture-add behaviours — how the candidate handles disagreement, how they collaborate across functions, how they make decisions under uncertainty. These are testable competencies. Vague "would I get a beer with them" culture fit is not a competency and shouldn't be in the rubric.