What is the difference between a competency matrix and a competency framework?

A competency framework defines the full set of competencies, their behavioral descriptions at each level, and how they map to job families. A competency matrix is a specific tool derived from that framework — it takes the competencies and arranges them in a grid against roles or employees. Think of the framework as the policy document and the matrix as the operational worksheet.

What is the difference between a competency matrix and a skills matrix?

A skills matrix inventories current-state capabilities — what skills employees have right now, useful for project staffing and training planning. A competency matrix defines required proficiency expectations per level and measures employees against those expectations. Skills matrices are descriptive (what is); competency matrices are normative (what should be).

How do you fill in a competency matrix for employees?

Start with the competency framework to identify the relevant competencies and proficiency levels for each role. During a performance review cycle, managers rate each employee on a 1–5 scale per competency based on observed behaviors, not general impressions. Self-assessments are often collected first and compared with manager ratings during calibration to surface divergence.

Can I use a competency matrix for hiring?

Yes. Competency matrices are widely used in structured interviews to create a role-specific assessment rubric. Interviewers score each candidate against the same competencies using the same proficiency scale, which makes post-interview comparisons objective and defensible. It removes the reliance on gut feel that drives a large portion of hiring bias.

What Is Competency Matrix? Definition & Examples

Q: What is a competency matrix?

A competency matrix is a table that maps roles or employees against a set of competencies — communication, technical depth, problem solving, and so on — with each cell showing either the required proficiency at a given level or the demonstrated proficiency of a specific employee. It gives managers and employees a shared, structured view of expectations and gaps.

What is a competency matrix?

A competency matrix — sometimes called a capability matrix or skills-and-competency matrix — is a structured table that maps either roles or employees against a defined set of competencies. Each cell in the grid contains a proficiency level: either what is required for a role at a given career level, or what a specific employee has currently demonstrated.

Used well, a competency matrix serves three distinct purposes. It makes promotion criteria explicit so employees understand exactly what the next level expects. It surfaces skill gaps so development plans target the right things. And it gives calibration sessions a shared reference point so managers across teams apply consistent standards.

Key components of a competency matrix

A well-built competency matrix has four elements working together:

Competency list. The rows of the matrix. These should be drawn from your competency framework — not invented per review cycle. Typical competencies include communication, technical depth, problem solving, delivery, ownership, collaboration, and leadership. The list for an individual contributor matrix differs from a management matrix.
Proficiency scale. A 1–5 scale (Foundational → Developing → Proficient → Advanced → Expert) works well across most organizations. Each number maps to a behavioral description in the framework, not just a vague label.
Role or employee axis. The columns. A role-based matrix shows required levels per job level (L1–L5); an employee-based matrix shows each person's current ratings.
Gap indicators. Calculated as required level minus demonstrated level. A positive gap means a development need; zero or negative means the employee meets or exceeds expectations for that competency at their current level.

Competency matrix vs. competency framework vs. skills matrix

Term	What it is	Primary use
Competency Framework	Defines competencies, behavioral descriptions per level, and job families	Source of truth — governs all evaluation
Competency Matrix	Grid of roles/employees × competencies with required or actual proficiency scores	Review calibration, promotion decisions, IDP targeting
Skills Matrix	Inventory of current team capabilities against required skills	Staffing, training planning, hiring gap analysis

A competency matrix requires a competency framework to exist first. A skills matrix is a standalone snapshot; it does not require level definitions or behavioral rubrics. Both tools are useful and complementary — many organizations maintain both. See our competency matrix template and skills matrix template to start with either.

How to use a competency matrix in performance reviews

The most common application is to rate employees against the competency matrix during a review cycle. The process works as follows:

Pull the matrix for the employee's role and level. A senior engineer should be evaluated against senior-engineer expectations, not the average across all engineers.
Collect self-ratings first. Ask the employee to rate themselves before seeing the manager's ratings. Self-manager divergence above one point on any competency is a signal worth discussing.
Manager rates based on observed behaviors. The behavioral descriptions in the framework anchor the ratings — "has she consistently demonstrated L3 ownership behaviors?" not "how do I feel about her performance?"
Use the matrix in calibration. When multiple managers discuss employees together, the matrix makes the conversation concrete. Disagreements surface as specific cell-level disputes, not vague impressions.
Use the gaps to drive IDPs. Any competency with a gap of 2 or more points is a natural focal point for the employee's development plan.

Common mistakes

Three patterns cause competency matrices to become shelfware:

Too many competencies. A matrix with 20+ competencies takes hours to complete and produces little signal. Eight to twelve competencies — divided between core (everyone) and functional (role-specific) — is the practical ceiling.
Vague behavioral descriptions. If the level-3 descriptor for "ownership" reads "takes responsibility," it is useless for calibration. Descriptions must be observable: "drives projects to completion without prompting and surfaces blockers before they become critical."
Reviewing the matrix once a year. A competency matrix becomes stale as roles evolve. A quarterly check-in — even just a 15-minute 1:1 discussion of one competency — keeps it alive and prevents review-season surprises.