Growth & Scaling
Competency Matrix: How to Build One (2026 Template)
A competency matrix maps the skills and behaviours each role needs, level by level. See a filled example, the skills matrix difference and 6 steps to build it.

Lead Talent Partner

A competency matrix is a grid that maps the competencies a role needs against proficiency levels, with an observable behaviour written into every cell. It tells a candidate, a hiring manager and a team lead the same thing: what good looks like at each level, and how you would recognise it.
By Mariia Chupryna. Reviewed by Andrew Demianenko, Head of Marketing at Matchr. Updated October 2026.
This guide is for recruiters, talent partners, HR teams and hiring managers who want a matrix people actually use. You will leave with a plain definition, the difference from a skills matrix and a competency framework, a filled example from our own Talent Sourcer grid, six build steps, and the part most guides skip: how to turn the matrix into better hiring decisions.
Key takeaways
- A competency matrix is a grid of competencies against proficiency levels, with observable behaviours in every cell.
- A skills matrix tracks what people can do today; a competency matrix describes how people perform a role at each level; a competency framework is the company-wide dictionary both draw from.
- Keep it short: five to eight competencies per role and three to five levels.
- Write behaviours, not adjectives. "Writes a working X-Ray search for GitHub" beats "strong sourcing skills".
- The matrix earns its keep in hiring: it becomes the interview scorecard and the language for calibrating a hiring manager's wish list against the market.
What a competency matrix is
A competency matrix has four parts, and each one does a job.
Competencies are the rows. A competency bundles skills, knowledge and behaviour into something you can see in the work: sourcing, stakeholder management, market insight. Skills are part of a competency, not a replacement for it, which is why skills-based hiring and competency matrices work well together.
Proficiency levels are the columns. Most teams use three to five, from entry level to expert, and often tie them to job titles or grades.
Behavioural indicators fill the cells. Each one describes what a person at that level does, in words a colleague could observe and check.
Ratings are how you score a person against the grid. A rating can be a level, a short text judgment or a number. The rating method is a choice you make; it is not what makes something a competency matrix.
Why build one now? Because roles move faster than job descriptions. The WEF Future of Jobs Report 2025 finds that employers expect 39% of workers' existing skill sets to be transformed or become outdated between 2025 and 2030, and 63% of employers name skill gaps as a major barrier to transforming their business. A matrix that describes the role as it was three years ago will hire for the past. Treat it as a living document with an owner and a review date.

Competency matrix vs skills matrix vs competency framework
The three terms are often used as if they mean the same thing. They do not, and mixing them up is how teams end up with a spreadsheet nobody trusts.
| Competency matrix | Skills matrix | Competency framework | |
|---|---|---|---|
| What it measures | How a person performs a role at each level | Which skills a person or team has today, and how well | The competencies the whole organisation values |
| Unit | One role or job family, competencies by levels | People by skills | Company-wide list with definitions |
| Who owns it | Hiring manager and team lead, with recruitment | Team lead or L&D | HR or People leadership |
| Typical use | Hiring scorecards, levelling, promotions, development plans | Staffing projects, training gaps, cover for absences | Values, leadership expectations, the shared dictionary |
| How often it changes | Every six to twelve months, or when the role changes | Often, as people learn | Rarely, with company strategy |
Our verdict: use a skills matrix to plan who covers what next quarter, a competency framework to agree on the language, and a competency matrix whenever you need to decide what level someone is at or should be hired at. One common myth is worth clearing up. A competency matrix does not require 360-degree feedback. Peer feedback is one way to rate people against the grid, and a useful one for development, but a hiring team rates candidates with interviews, work samples and references instead.
A filled example: our Talent Sourcer matrix
Here is a shortened version of the grid we use for sourcing roles at Matchr. It has five competencies and four levels, from Associate Talent Sourcer to Lead Talent Sourcer. Every cell holds one behaviour you could check in a working week. Our full grid has more indicators per cell; this is the core.
| Competency | Associate Talent Sourcer | Talent Sourcer | Senior Talent Sourcer | Lead Talent Sourcer |
|---|---|---|---|---|
| Search craft | Writes a working Boolean string with AND, OR, NOT, brackets and quotes | Writes X-Ray searches for LinkedIn and GitHub with the site: operator | Builds searches across several platforms with site:, filetype:, intitle: and inurl:, including diversity-aware searches | Designs a search approach for a new platform or a niche market and teaches it to the team |
| Platform knowledge | Uses LinkedIn search and knows where else relevant candidates gather | Uses LinkedIn Recruiter or Sales Navigator projects well and searches GitHub and Google | Uses GitHub, Meetup, Stack Overflow and community channels as regular sources; maps talent with company databases | Picks the right mix of tools for each search and knows non-standard methods, including basic open-source intelligence |
| Market insight | Reports what the search returns: volumes, titles, locations | Explains why a pool is small or large and which titles the market uses | Tells the hiring manager what the brief will cost in time and pay, with evidence | Shapes the hiring plan with market data before the role opens |
| Outreach | Sends personalised messages from a template | Writes messages that earn replies and follows up with care | Runs multi-step outreach for hard roles and adjusts the message from the replies | Sets the outreach standards and coaches others on tone and response rates |
| Stakeholder management | Shares updates on time with the recruiter | Runs intake notes with the recruiter and the hiring manager | Leads calibration with the hiring manager and pushes back with data | Advises leaders on hiring plans and resolves conflicts between teams |
How to read it. A person rarely sits on one level across every row. A strong Talent Sourcer may already search like a senior but still need help leading a calibration conversation. That is the point: the matrix shows where to coach, not just which title to give.

Notice what is missing. There is no row for "resilience" or "creativity". Those qualities matter, but as rows they are too vague to rate. When they show, they show inside the behaviours: the follow-up that earns a reply, the search approach for a market nobody has mapped. For a broader view of what makes a great sourcer, see what an extraordinary sourcer looks like.
The levels also carry focus. At the first three levels the work is execution. At the lead level it becomes execution plus facilitation: setting standards, teaching and shaping the plan.
How to build a competency matrix in 6 steps
Building a matrix from scratch takes a small project team, not a single HR owner. Recruitment usually drafts, leaders and hiring managers shape, field experts check the hard skills, and L&D or HR turns the result into everyday tools. The six steps below show who does what at each point.
| Who | Their part |
|---|---|
| Recruitment or talent acquisition | Drafts the first list of competencies, brings market data, turns the matrix into scorecards |
| Hiring managers and team leads | Cut and sharpen the list, agree the levels, own the matrix for their team |
| Field experts | Check that technical indicators match the real work and today's tools |
| L&D and HR | Turn the matrix into onboarding, development plans and review guidelines |
Appoint one project lead who sets the purpose, the timeline and the review date. Without one, the matrix drifts between teams and nobody signs it off.

Step 1. Set the purpose
Decide what the matrix is for before you write a single row. Hiring, levelling, promotions and development plans each need a slightly different level of detail. A matrix built for hiring needs indicators you can test in an interview. A matrix built for development needs indicators a manager sees over months. Write the purpose at the top of the document and name the owner.
Step 2. Pick the roles
Start with one role or one job family, ideally one you hire for often. A sourcing team, a group of account executives or a set of backend engineers is enough. Once the first matrix works, the second takes a fraction of the time.
Step 3. List five to eight competencies with the hiring manager and the team
Recruitment drafts a first list from the job description, the intake conversation and market research. The hiring manager and two or three people in the role then cut and sharpen it. Expect disagreement here: hiring managers often want every skill they have ever seen in a great hire. Bring the market into the room. Show how many people hold that combination of skills, how long similar searches took and what they cost. A focused list makes a shorter, fairer interview process.
Step 4. Write behavioural indicators for each level
This is the step that makes or breaks the matrix. For every competency and every level, write one or two behaviours a colleague could observe. Use verbs. Avoid "good", "strong" and "excellent", because nobody agrees on what they mean. Field experts check that the technical indicators match the real work and the current tools.
Here is the difference in practice, for the market insight row at senior level:
| Vague indicator | Observable indicator |
|---|---|
| Has strong market knowledge | Tells the hiring manager what the brief will cost in time and pay, with evidence from the search |
| Good at stakeholder management | Leads the calibration meeting and changes the brief when the data says the level is wrong |
| Excellent communicator | Writes intake notes the recruiter and the hiring manager both sign off without edits |
A useful test: could two different interviewers watch the same week of work and agree whether the behaviour happened? If not, rewrite the cell.
Step 5. Choose the rating scale
Pick one scale and use it everywhere. Proficiency levels tied to the columns are the simplest. Text judgments add context. Numbers help with analysis but can give a false sense of precision. Whatever you choose, ask raters to note the evidence behind each rating, and never let a total score decide a level on its own.
Step 6. Pilot, write the guidelines and review on a fixed date
Test the matrix on a few current team members and two or three live hires. Fix the cells people misread. Then write short guidelines: what each level means, how to rate, who to ask. L&D and HR take it from here into onboarding, development plans and reviews. Put a review date in the calendar, every six to twelve months or sooner when the team or the market shifts.
Using the matrix in hiring
This is where a competency matrix does its most valuable work, and where most guides stop short.
Turn it into a scorecard. Each competency becomes a row on the interview scorecard, and each level becomes the anchor for the rating. Interviewers stop scoring "culture fit" or "gut feel" and start scoring the same behaviours, against the same descriptions. Split the rows across the interview loop so each interviewer owns two or three competencies, and use skills assessments at the top of the funnel for the ones a work sample tests better than a conversation.
Write competency-based questions. For each row, write one question that asks for a real example, and use the STAR method (Situation, Task, Action, Result) to probe it. For search craft: "Tell me about a search where the obvious platforms ran dry. What did you try next, and what did it return?" Some teams use PARLA (Problem, Action, Result, Learning, Application) to add what the candidate learned.
A scorecard row for the Talent Sourcer example looks like this:
| Competency | Question | Level needed | Evidence heard | Rating |
|---|---|---|---|---|
| Search craft | Tell me about a search where the obvious platforms ran dry | Talent Sourcer | Built an X-Ray search on GitHub, found a pool the team had missed | Meets |
| Market insight | When did the market tell you a brief was wrong, and what did you do? | Senior Talent Sourcer | Reported pool sizes, did not challenge the brief | Below |
The evidence column matters more than the rating. It lets the debrief compare what people actually heard instead of arguing over scores.
Calibrate the hiring manager's wish list against the market. Before the role opens, walk through the matrix with the hiring manager and mark the level you are hiring for on every row. Then test it against the talent pool. This is the conversation that saves weeks. The way recruiters work with hiring managers at this stage decides how fast the search moves later.
As a global embedded RPO partner, we at Matchr see one pattern again and again inside our clients' teams: the matrix says mid-level, the market says senior. A brief that asks for senior behaviours on five of five rows will not be filled at a mid-level salary, however good the employer brand. Because our recruiters sit inside the client's systems and meetings, we can show the gap with live data from the search and agree which two or three rows truly need the senior level. The rest become things the new hire grows into. That is the matrix doing its job: a shared language, not a wish list.
Where AI helps and where judgment decides
Software is good at parts of this work. It can match skills evidence in a CV to the rows of your matrix, score a technical assessment, flag inconsistent ratings across interviewers and keep the matrix itself up to date with new tools and titles.
Other calls stay with people. Deciding which level a candidate is at across several rows, weighing potential against current skills, and reading context (a career break, a career change, a small company where one person did five jobs) are judgment calls. Sometimes advanced soft skills and high potential outweigh a gap in hard skills. A tool cannot make that trade on its own.
There is also a legal line. The EU AI Act lists in Annex III as high-risk the AI systems used to recruit or select people, including those that filter applications and evaluate candidates, and the systems used to monitor and evaluate the performance of workers. If an AI tool rates people against your competency matrix, treat it as high-risk: keep a human decision on every level call, document how the tool scores, and tell candidates and employees when AI is involved. Leaders on our podcast make the same point about hiring for skills, not resumes: the tool widens the view, people decide.
Common mistakes and signs your matrix needs a rebuild
Most failed matrices fail for the same few reasons:
- Too many competencies. Twenty rows means nobody rates them honestly. Keep five to eight.
- Vague indicators. "Communicates well" at every level is a description of nothing. Each level needs a different, observable behaviour.
- Numbers without context. A total score hides the row that matters most for the role. Read the rows, not the sum.
- No owner. A matrix without an owner and a review date goes stale within a year.
And the signs it is time to rebuild:
- It is not moving the numbers it was built for: time to hire, quality of hire or retention for the role stay where they were.
- New hires struggle in probation with the real work, or find it so easy they lose interest.
- The market reads your levels differently. You are hiring for mid-level, but candidates and competitors call that profile senior.
- It is inconvenient. Interviewers take too long to write up their notes, or employees cannot see how to move up a level.
For how talent leaders expect hiring to change next, and which roles they plan for, see what talent leaders told us in our Talent Acquisition Trends 2026 report. If those changes touch a role you hire for often, its matrix is due for a review.
Templates and public examples
Templates save time, but none was built for your company. Use one as a starting structure, then rewrite every indicator in your own words and for your own roles. The Miro team competency matrix template is a simple visual starting point.
Public engineering ladders are the best free examples of finished matrices:
- GitLab: individual contributor levels described in the open handbook.
- Dropbox: a full career framework with behaviours per level.
- Wise: an engineering career map that links levels to impact.
- SoundCloud: a short, readable take on engineering levels.
- Klarna: engineering competences written for candidates.
Read two or three before you write your own. Notice how the best ones describe behaviour, not personality.
FAQ
What is a competency matrix?
A competency matrix is a grid that maps the competencies a role needs against proficiency levels, with an observable behaviour in every cell. Teams use it to hire, level, promote and develop people against the same description of good work.
What is the difference between a competency matrix and a skills matrix?
A skills matrix records which skills people have today and how well. A competency matrix describes how a role is performed at each level, combining skills, knowledge and behaviour. Use the skills matrix for staffing and training, the competency matrix for hiring and levelling.
What is the difference between a competency framework and a competency matrix?
A competency framework is the organisation-wide list of competencies and their definitions. A competency matrix applies part of that list to one role or job family and spells out each level.
How many levels should a competency matrix have?
Three to five levels work for most roles. Fewer than three hides real differences; more than five makes the levels hard to tell apart and slows every rating.
How do you use a competency matrix in hiring?
Turn each competency into a scorecard row, write one competency-based question per row, and agree with the hiring manager which level the role needs on each row before the search starts. Then test that level against the talent market.
How often should you update a competency matrix?
Review it every six to twelve months, and sooner when the role, the team or the tools change. Give it a named owner and a fixed review date.
A shared language, not a scorecard
A competency matrix is not a test people pass or fail. It is a shared language between the people who hire, the people who manage and the people who grow in the role. When everyone describes good work the same way, hiring gets faster and growth gets fairer.
Need help building one for a role you are hiring for? Let's get in touch.