Ask five managers what a "career framework" is and you will hear about a spreadsheet, a list of titles, a set of competencies, a pay structure and a promotion policy. They are all describing part of the same thing. The confusion is harmless in conversation and expensive in practice: one team builds a list of titles and calls it done, another builds a fifty-row competency grid that nobody can map to a job.
This article untangles the vocabulary — career ladder, career framework, competency matrix, job levels and grades — and shows how the pieces fit for one department of a 20–200-person company. If you already know the terms and want the method, go straight to how to build a career ladder.
The short answer
Each term answers a different question:
| Term | The question it answers | Example |
|---|---|---|
| Career ladder | Which roles can I move through? | Coordinator Manager Senior Manager |
| Career framework | What is expected of me, and on which paths? | Two tracks, five levels, six competencies for Marketing |
| Competency (skills) matrix | What exactly does each level require? | "Campaign planning" described for levels 1 to 5 |
| Job level | How senior is this role compared to others? | Level 3 |
| Grade (or pay band) | What do we pay for this level? | A salary range attached to level 3 |
The ladder is the path. The framework is the path plus the expectations. The matrix is the expectations laid out as a grid. Levels are the rungs, and grades are what you pay on each rung.
Career ladder: the path
A career ladder is an ordered sequence of roles in one line of work. "Support Associate Support Specialist Senior Specialist Support Lead" is a ladder; so is "Junior Designer Designer Senior Designer Lead Designer".
A ladder on its own answers "what comes next?" but not "what do I have to do to get there?". That is why a ladder that is only a list of titles rarely changes anything: people can see the next rung but not the distance to it.
A department can have more than one ladder. The common case is a pair: one for people who grow as specialists and one for people who grow by leading others. That pair is usually called a dual career ladder, and the two halves are called tracks.
Career framework: ladders plus expectations
A career framework is the complete structure for one department: its tracks, the levels on each track, the role that sits on each level, and the competencies every role is measured on, described for each level.
Put simply, a framework turns a ladder into something you can assess against. For a five-person sales team, the framework might be one track with three levels and five competencies. For a 30-person engineering department, it is more likely two tracks, five levels and six competencies.
Two properties separate a working framework from a document:
- Every role has written expectations. Not adjectives — what someone at that level actually does.
- Levels are comparable across tracks. Level 4 on the specialist track carries roughly the same scope and weight as level 4 on the management track.
Some companies have one framework per department; others try one framework for the whole company. In practice a shared structure (the same number of levels, the same shared competencies) with a separate framework per department works best, because "senior" in sales and "senior" in engineering describe different work.
Competency matrix: the grid
A competency matrix — also called a skills matrix — is the framework's expectations laid out as a table: competencies down the side, levels across the top, and a short description in every cell.
Here is one row from a customer support matrix:
| Competency | Level 1 | Level 2 | Level 3 |
|---|---|---|---|
| Written communication | Uses saved replies correctly and asks for review on anything unusual | Writes clear replies that usually resolve the issue in one message | Writes the help-centre articles and macros the rest of the team relies on |
The matrix is the part people actually read during a career conversation, because it is specific. A ladder says "you are a Support Specialist"; the matrix says "to reach the next level, your written communication needs to move from resolving issues to setting the standard for others".
Two practical notes:
- Competency or skill? The words are used interchangeably. "Competency" tends to describe a broad area (communication, ownership), "skill" something narrower (SQL, negotiation). What matters is that each row is described per level.
- Not every role needs every row. A support lead may need a people-leadership row that a level 1 specialist does not. A good matrix allows an empty cell rather than inventing an expectation.
Job levels, grades and titles
These three get confused most often, especially in pay discussions.
A job level is the rung itself: a number or short label (L1–L5) that says how senior a role is relative to others. Levels are what make roles in different departments comparable — a level 3 support specialist and a level 3 engineer should carry similar scope within their fields.
A grade usually means a pay grade or band: the salary range attached to a level. In many small companies grade and level line up one to one, which is why "job levels vs grades" is such a common search. Larger organisations sometimes have more grades than levels, so that pay can move within a level without a promotion.
A job title is the name on the contract and the CV: "Senior Account Executive". Titles face the market; levels are internal. Keeping them separate means you can change the framework without renaming people, and you can use market-standard titles without inventing a level for each.
How the pieces fit together: one department
Take the marketing team of a 70-person software company: seven people, one of whom manages the others.
The ladder. Today there are three titles in use — Marketing Coordinator, Marketing Manager, Head of Marketing — and two people with "Senior" added to their title at different points in time.
The tracks. The team agrees on two: a specialist track for people who grow by owning bigger channels and campaigns, and a management track that starts at level 3.
The levels. Four on the specialist track: Coordinator (1), Marketing Manager (2), Senior Marketing Manager (3), Principal Marketer (4). The management track has Marketing Lead (3) and Head of Marketing (4).
The competencies. Six rows: campaign planning, content and messaging, channel expertise, analytics, collaboration with sales, and helping others grow. The last one is shared with every other department; the first five are marketing's own. The ready-made marketing manager template is a good starting point for them.
The matrix. Every competency is described for each of the four levels. The cell for "analytics" at level 2 reads: "Reports on the results of their own campaigns and explains what they would change next time." At level 4: "Sets how the team measures marketing and is the person sales and finance ask when numbers disagree."
The grades. Once the levels have settled, the CEO attaches a salary range to each role. Nobody's pay changes on the day the framework is published.
Put together, the ladder, tracks, levels, competencies and matrix form one career framework for one department. The customer support template and the software engineer template show the same structure for two other departments.
Which one to build first
If you have nothing yet, do not start with the matrix — start with the structure, then fill it in:
- Levels and tracks. Decide how many levels and whether you need a second track. The guide on how many levels a career ladder should have covers the first decision.
- Roles on each level. Put one role on every level of every track, using titles people already recognise.
- Competencies. Pick five to eight rows per department.
- The matrix. Write what each level looks like for each competency. This is most of the work.
- Pay. Attach ranges to roles once the expectations have been used in a round of career conversations.
If you already have pieces — a list of titles here, a skills spreadsheet there — check what is missing against this list. The most common gap is step 4: titles and pay bands exist, expectations do not.
In LadderKit these map to the career ladder of each department (tracks, levels and roles, in draft until you publish) and its skills matrix, which sets the level each role needs and is what check-ins assess against.
Common mix-ups
- Calling a list of titles a framework. Without expectations per level, people still cannot tell what the next step asks of them.
- A matrix without roles. Fifty competencies described for five levels, but nobody knows which cells apply to their job.
- Treating grades as levels. If the only difference between two "levels" is pay, you have pay steps, not career levels. That is fine — just call them that.
- One framework for every department. Shared competencies are a good idea; shared expectations for sales and engineering are not.
- Renaming people with every revision. Keep titles stable and map them to levels. Change the framework as often as you need to.