Data and analytics
Data Analyst
Five levels from Junior to Principal Analyst, across seven competencies from framing questions to changing decisions.
- 5 levels
- 7 competencies
Skills matrix
Write down what each skill looks like at every level, set the level each role needs, and give everyone a clear view of their role.
Free plan · No credit card required
How it works
Write a skill with a description of every level and examples of what that level looks like in practice. Start from scratch, from a built-in skill, or by duplicating one that is close.
Pull skills into a department's framework, sort them into groups such as Craft or Leadership, and set the level each role needs. Leave a cell empty when a role doesn't need the skill.
A role card brings it together: the role's description, the skills it requires with their levels, and its salary ranges — exportable as a PDF.
The matrix is what people are reviewed against: a check-in pulls in exactly the cells of the person's own role, so nobody is rated on a skill their role does not need.
Permissions
Good to know
Keep exploring
Data and analytics
Five levels from Junior to Principal Analyst, across seven competencies from framing questions to changing decisions.
Engineering
Four levels from Junior QA to Lead QA Engineer, across six competencies from test design to quality practices.
Design
Five levels from Junior Designer to Head of Design, across six competencies from research to design systems.
For tech companies
For CTOs and department heads at 50–200-person tech and SaaS companies who need levels that mean the same thing in every team.
A practical, seven-step method for companies of 20 to 200 people: tracks, levels, competencies, expectations, calibration and rollout — with a worked example and the mistakes to avoid.
Updated 1 October 2026
Four to six levels per track covers most companies of 20 to 200 people. How to pick the number for yours, the signs you have too few or too many, and how to add a level later.
Updated 1 October 2026
FAQ
For practical purposes, yes. LadderKit calls the rows skills; each has a description per level, and the matrix sets which level every role expects.
No. Leave a cell empty and the skill is simply not required for that role, so it won't appear in that role's check-ins.
Yes. A skill lives in the organisation's library and can be added to several departments' frameworks, each setting its own required levels.
The role's name, level and description, every required skill with its level description and examples, and its salary ranges. Section headings are in English.
Not directly, because the built-in skills are shared by every organisation. Duplicate one and the copy is yours to edit.
Start free and build your first skills matrix from the built-in skills.
Free plan · No credit card required