Competency Model vs Career Framework: How They Work Together
By Career Ladder Builder
Why two HR teams can use the same words and mean completely different things
A Director of People at a 90-person professional-services firm and an HR Manager at a 55-person SaaS company both say their organization has "competencies." Ask a follow-up question — "Where are they written down? How do employees know what the expectation looks like at their level? How do you score against them consistently?" — and the answers often diverge fast.
One team has a slide deck from a prior consultant. The other has a tab in a spreadsheet last edited two years ago. Neither is wrong about having competencies; both are missing the structure that turns a list of qualities into an actual evaluation system.
The confusion usually traces to two terms being used interchangeably when they describe different — and complementary — things: a competency model and a career framework. Understanding what each one does, and where the line between them falls, is the prerequisite for building an evaluation process you can defend in a promotion conversation, a pay discussion, or a legal review.
By the end of this article, you will have a clear working definition of each concept, a concrete picture of how they connect, and a practical path for building both together.
What a competency model actually is
A competency model is a defined set of skills, behaviors, and knowledge areas that an organization has identified as essential to effective performance in a given role or job family. It answers one question: What does good look like here?
Each item in a competency model is typically expressed as a competency statement — a behavior-anchored description that makes the quality observable and measurable rather than aspirational and vague. "Strong communicator" is not a competency statement. "Tailors written and verbal communication to the audience's level of technical familiarity, asking clarifying questions before presenting a recommendation" is closer to one. (For a deeper look at writing these well, see our guide to writing competency statements.)
A competency model typically covers some combination of:
- Core or universal competencies — qualities expected of everyone in the organization (e.g., collaboration, accountability, communication)
- Functional or technical competencies — role- or job-family-specific knowledge and skill (e.g., financial modeling for a finance analyst, incident response for a site reliability engineer)
- Leadership competencies — behaviors expected of people managers and senior individual contributors (e.g., developing others, setting direction, managing through ambiguity)
What a competency model does not tell you is: how the expectation changes as someone moves from associate to senior to principal, or from an individual-contributor path to a management path. That is where the career framework comes in.
What a career framework actually is
A career framework (sometimes called a job architecture or career ladder) is the structure that organizes roles, levels, and advancement criteria across an organization. It defines how many levels exist in a given job family, what distinguishes each level from the one above and below it, and — critically — what growth looks like for employees who want to advance as individual contributors versus those who want to move into management.
If a competency model answers "what does good look like?", a career framework answers "good at what, at which level, in which track?" See our full explainer on what a career framework is if you are building one from scratch, and our comparison of career framework vs. job architecture if you are working through terminology with a leadership team.
A typical career framework includes:
- Job families — groupings of related roles (Engineering, Marketing, Finance, Customer Success)
- Career levels — named or numbered stages within a family (Associate → Mid-level → Senior → Staff/Lead → Principal/Director)
- IC and Manager dual tracks — separate advancement paths so that a senior engineer can grow to principal without being forced into management, and a manager can be evaluated on different criteria than an individual contributor at the same pay band
- Level descriptors — the scope, impact, and autonomy expected at each level, distinct from the competency statements themselves
The career framework is the scaffolding. The competency model is the material you install inside it.
How competency model vs career framework fit together
Here is the relationship in plain terms: a competency model defines the dimensions of performance; a career framework defines the levels at which performance is evaluated across those dimensions.
Picture a grid. The columns are your career levels (Associate, Mid, Senior, Staff). The rows are your competencies (Technical Skill, Communication, Collaboration, Judgment). Each cell in that grid is a leveled competency statement — a description of what that competency looks like, specifically, at that level.
A competency model without a career framework gives you a list of qualities with no progression. A career framework without a competency model gives you level titles with nothing observable to evaluate. Combined, they give you a defensible evaluation system.
A few examples of how the two layers work together:
Communication — Associate level: Communicates status on assigned work proactively; asks for clarification before tasks diverge from scope.
Communication — Senior level: Drives alignment across stakeholders with competing priorities; structures complex recommendations for both technical and non-technical audiences without losing precision.
Communication — Principal/Staff level: Sets communication norms for the team; translates organizational strategy into actionable context for ICs; identifies and resolves misalignment before it affects delivery.
The competency (Communication) is the same row across all three. The career framework provides the column — the level — that determines what the expectation actually looks like in practice. Neither is useful without the other.
Why the distinction matters for HR teams at growing companies
For a 30-person company, a single-page list of values may be sufficient to have a meaningful performance conversation. By 60 employees, inconsistency creeps in: two managers evaluate the same behavior differently because they are using different mental models of "senior." By 100 employees, that inconsistency is a fairness and legal-exposure problem — particularly in promotion and compensation decisions.
A few practical risks that emerge when organizations have one piece but not both:
Competency model without a career framework: Evaluators apply the same behavioral expectations to an associate and a senior employee, making meaningful differentiation impossible. Promotion criteria become subjective ("she just feels ready"), which is exactly the fact pattern that draws scrutiny in disparate-impact claims. If you are subject to U.S. employment law, you should confirm your evaluation practices with qualified employment counsel — the EEOC notes that Title VII applies at 15 or more employees and covers employment decisions including promotions.
Career framework without a competency model: Level titles and pay bands exist, but there is nothing behavioral to evaluate against. Managers give ratings based on output or tenure rather than demonstrated competencies, and the company cannot identify skill gaps systematically or build targeted development plans. High performers who cannot see a specific, behavior-anchored path to the next level tend to conclude the path does not exist — and they leave.
According to Pew Research Center (2022), 63% of workers who quit in 2021 cited no opportunities for advancement as a reason — tied with low pay. A career framework and competency model, working together, are the structural response to that driver.
Building the two layers together: a practical sequence
Organizations that try to build a competency model and a career framework in isolation — or in the wrong order — typically stall at the point where the two need to connect. Here is a sequence that avoids that.
Step 1: Define your job families. Group roles that share a skill domain and logical advancement path. Engineering, Product, Marketing, Sales, Customer Success, Finance/Operations, and People are common starting points. This is your career framework's first column.
Step 2: Set your level architecture. Decide how many levels each job family needs — typically four to six for an organization under 200 employees. Define each level by scope and impact (e.g., "operates within defined tasks" → "scopes and executes projects independently" → "influences direction across teams"). Set up IC and Manager dual tracks where relevant. You can explore starter templates in our career ladder templates hub.
Step 3: Identify your core and functional competencies. For each job family, define the competency dimensions that matter most for effective performance. Limit functional competencies to the handful that genuinely differentiate performance — five to eight per job family is a practical ceiling. Core competencies that apply organization-wide (collaboration, communication, accountability) can be defined once and leveled across all families.
Step 4: Write leveled competency statements for each cell. This is the integration point — the work that produces the grid described above. Each statement should describe observable behavior, be calibrated to the level's scope expectation, and use consistent verb and evidence conventions across the grid. Our guide to writing competency statements covers the mechanics in detail.
Step 5: Validate with managers before you go live. Run a calibration session with two or three managers using real (anonymized) employee examples. If two managers applying the same rubric arrive at materially different scores for the same behavior, the statement needs more specificity. Calibration before launch is far easier than re-calibration after the first review cycle runs.
If you are building from scratch or inheriting a blank slate, our Competency Library Starter Kit provides 50 pre-built, O*NET-sourced competency statements across five common job families — a practical starting point for Step 3 and Step 4 before you customize to your organization's specific context.
This product references occupational content from O*NET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). O*NET data is used under CC BY 4.0.
Common mistakes that break the connection
Treating the competency model as a values list. "Acts with integrity" is not an evaluable competency statement — it is an aspiration. Competency statements need to describe behavior specific enough that two evaluators independently observing the same employee can arrive at the same score.
Letting level descriptors and competency statements do each other's job. Level descriptors belong in the career framework and describe scope, autonomy, and impact at a level. Competency statements belong in the competency model and describe behavior on a specific dimension. Mixing them produces confusion in scoring: is this employee being evaluated on what they do or on how broadly they do it?
Building a competency model for only one track. If your organization has both individual contributors and managers, a Manager at Level 4 needs different competency expectations than an IC at Level 4 — specifically around developing others, team accountability, and organizational influence. A single undifferentiated competency model forces managers to be evaluated on IC behavior and vice versa, which undermines both.
Skipping the connection to development. The point of combining a competency model with a career framework is not only to produce defensible evaluations — it is to produce a specific, actionable gap report that an employee and their manager can work from. If the leveled competency grid cannot generate a "here is what you are doing well and here is the specific behavior that would demonstrate readiness for the next level" conversation, it is doing only half its job.
For a deeper look at how O*NET's occupational data can accelerate the competency-building step, see our explainer on the O*NET competency framework.
The practical next step
If your organization has competencies but no career framework, or a career framework with no behavioral competency layer, the gap between what you have and a defensible evaluation system is bridgeable — but it requires deliberately building both pieces and connecting them into a single grid.
Start with the job families and level architecture (your framework), then add the behavioral layer (your competency model), and write the leveled statements that fill the grid. Validate with managers. Run one cycle. Iterate.
To accelerate the competency-writing step, download the Competency Library Starter Kit — 50 O*NET-sourced statements across five job families, formatted for direct use or adaptation inside Career Ladder Builder or your own tooling.
Enjoying this? Get more HR development guides in your inbox.
