Competency framework
A structured set of skills, behaviours, and knowledge areas that define what good looks like at each level of a role, used as the shared reference point for hiring, performance reviews, and development planning.
Michal Juhas · Last reviewed May 23, 2026
What is a competency framework?
A competency framework is a structured set of skills, behaviours, and knowledge areas that defines what good looks like at each level of a role. It is the shared reference point that turns hiring from a subjective conversation into a comparable, evaluable process. When a panel of interviewers all use the same framework, a candidate's answers map to the same criteria regardless of which interviewer is in the room, and decisions become easier to explain and audit.
In practice
- A hiring panel at a 500-person company rates the same candidate as a "strong yes" and a "pass" in the same round because they are each thinking of a different previous hire when they say "good problem-solver." A competency framework with written behavioural anchors closes that gap.
- A recruiter uses the framework to write structured interview questions before sending a guide to the hiring manager, so every candidate is asked the same questions in the same order.
- A TA ops lead says "we need to update the framework" after noticing that three of the five competency questions in a software engineering scorecard are never answered with high scores by even the strongest hires: a signal the criteria no longer reflect what the role actually needs.
Quick read, then how hiring teams use it
This is for recruiters, sourcers, TA, and HR partners who need the same vocabulary in debriefs, vendor calls, and policy reviews. Skim the first section when you need a fast shared picture. Use the second when you are deciding how it shows up in the ATS, sourcing tools, or candidate evaluation.
Plain-language summary
- What it means for you: A written list of the specific skills and behaviours that define a strong hire for a given role, with descriptions of what each looks like at different levels of seniority.
- How you would use it: Write your interview questions from the framework, train interviewers to map candidate answers to the anchors, and use the scores in your hiring decision debrief.
- How to get started: Pick one role you hire frequently. List the 5 things a great performer in that role does that an average performer does not. Write what each looks like in a behavioural interview answer. That is your draft framework.
- When it is a good time: Any time you have more than one interviewer evaluating candidates for the same role and you want their scores to mean the same thing.
When you are running live reqs and tools
- What it means for you: A competency framework is the input that drives consistent scorecards, structured interview guides, calibration sessions, and eventually defensible pass-rate data if your process is audited for fairness.
- When it is a good time: Before you start interviewing for a new role family, when you are redesigning a hiring process that is producing inconsistent quality, or when pass-rate data shows potential adverse impact that might be driven by inconsistent criteria.
- How to use it: Map each scorecard dimension to a specific competency. Write question and anchor combinations that can be consistently rated by different interviewers without prior calibration. Run a calibration session before each new hire cohort begins.
- How to get started: Pull your five most recent scorecards for one role. Count how many dimensions had written anchors versus free-text notes only. Any dimension with free-text only is a candidate for framework formalisation.
- What to watch for: Frameworks that are so long that interviewers skip questions, competencies that correlate with demographic proxies (cultural fit, communication style as proxies for accent or background), and frameworks that are never updated when the role changes substantially.
Where we talk about this
On AI with Michal live sessions the AI in recruiting track covers how to build scorecards from a competency framework and how AI tools are beginning to assist with behavioural anchor writing. See AI in recruiting workshops.
Around the web (opinions and rabbit holes)
Third-party creators move fast. Treat these as starting points, not endorsements.
YouTube
- Search "competency framework design HR" for practitioner walkthroughs of framework-building workshops used in talent acquisition and performance management.
- Search "structured interview design" for videos that show how competency frameworks translate directly into question and anchor format.
- r/humanresources has threads on building competency frameworks from scratch, including disagreements about whether generic frameworks or role-specific ones produce better outcomes.
- r/recruiting covers the practitioner side: how recruiters actually use frameworks in practice versus how L&D teams design them.
Quora
- How do you create a competency framework for a company? collects answers from HR practitioners on scope, validation, and rollout.
Framework versus job description
| Element | Job description | Competency framework |
|---|---|---|
| Purpose | Attract candidates | Evaluate candidates |
| Audience | Job seekers | Hiring panel |
| Format | Public prose | Internal rubric |
| Updated | Per req | Per role family annually |
Related on this site
- Glossary: scorecard, calibration session (hiring), behavioral interview
- Glossary: structured interview, adverse impact, human-in-the-loop
- Glossary: AI bias audit, talent acquisition metrics
- Live cohort: AI in recruiting workshops
- Membership: Become a member
Frequently asked questions
What is a competency framework in hiring?
A competency framework is a documented set of behaviours and skills that define performance expectations for a role or role family, organised by level. In hiring, it translates into the criteria that a scorecard measures and the anchors that interviewers use to rate candidate responses. Without a competency framework, interview panels use different mental models for what qualifies as a strong answer, which leads to inconsistent decisions and makes it hard to audit for adverse impact. With one, a candidate response can be mapped to a specific observable behaviour and rated consistently across interviewers.
How does a competency framework improve structured interviews?
A structured interview draws its questions directly from the competency framework: each question targets a specific competency, and each answer is rated against a pre-written rubric that describes what a weak, acceptable, and strong response looks like. This makes scoring reproducible. Two interviewers rating the same candidate on the same question should arrive at similar ratings because they are comparing to the same anchor, not to their personal experience of past hires. Calibration sessions are used to check whether interviewers are applying the framework consistently before live interviews begin.
What makes a competency framework too vague to be useful?
Vague frameworks describe traits rather than behaviours: "strong communicator", "strategic thinker", "collaborative" appear in nearly every framework and tell an interviewer nothing about what to listen for. A useful competency describes a specific observable action: "explains technical trade-offs in plain language when speaking with non-technical stakeholders" is evaluable. "Good communicator" is not. When calibrating on a new framework, ask your panel to give one concrete example of a candidate behaviour that would score a 4 out of 5 on a given competency. If they cannot agree on an example, the competency needs rewriting before interviews start.
How should competencies be levelled across career stages?
Levelling means defining how the same competency looks at different seniority levels. A junior software engineer "writes code that passes peer review with minor comments" while a staff engineer "sets the technical standards the team reviews against." The gap between levels should be specific and distinguishable, not just a description of doing the same thing with more experience. In practice, most frameworks use 3 to 5 levels per competency, matching the organisation's job architecture. The clearer the level descriptors, the easier it is to write interview questions that differentiate candidates accurately between adjacent levels.
Can AI help build or maintain a competency framework?
AI can accelerate the drafting phase: generating an initial list of competencies and behavioural anchors for a role family based on job description inputs, industry benchmarks, or a few example job levels you provide. It will not surface the unspoken norms your organisation actually cares about, and it tends to produce frameworks that are comprehensive on paper but too long to use reliably in interviews. Use AI to create a first draft of 8 to 12 competencies, then run a calibration session with a panel of strong performers and managers to cut it to the 4 to 6 that are genuinely predictive for the role.
How do we keep a competency framework current?
Review the framework every 12 to 18 months and immediately when the role substantially changes (new technology stack, change in team scope, shift from IC to leadership track). Trigger points: if interviewers consistently skip certain competency questions because they seem irrelevant, if new hires are thriving or struggling on dimensions the framework does not capture, or if your quality-of-hire scores on new hires are diverging from their interview ratings. Keep a changelog with the date of each revision and the reason, so compliance teams can answer questions about how the hiring criteria evolved over time.
Where does a competency framework come up in AI with Michal workshops?
Competency frameworks come up in the AI in recruiting track when we discuss how to build scorecards that work with AI-assisted interview tooling, and in the structured hiring module where we show how a well-defined framework produces better calibration session outputs and more defensible hiring decisions. Bring your current job description and any existing scorecard: the room conversation is faster when grounded in real criteria rather than hypotheticals. See AI in recruiting workshops and review scorecard and calibration session for the tooling that sits alongside the framework.