A framework per department, one shape for all
Each department owns its framework — drafted, edited by the people you assign, then published — but every framework uses the same building blocks: tracks, levels, roles and skills.
For tech companies
Keep levels, promotion criteria and salary ranges consistent across engineering, product, design and every other department — and use them in the check-ins people actually have.
Free plan · No credit card required
Sounds familiar?
Engineering has five levels, sales has three, and design has titles nobody can compare. Two people doing similar work get different outcomes depending on which manager writes the promotion case.
Strong engineers and designers become reluctant managers because there is no individual-contributor track, or it stops too early.
Pay is set at the offer and drifts from there. Nobody can say which range belongs to which role, so every pay review starts from scratch.
Managers run reviews from memory and a blank document, so feedback is hard to compare and hard to act on.
How LadderKit helps
Shared building blocks, owned by each department, and used in the conversations that matter.
Each department owns its framework — drafted, edited by the people you assign, then published — but every framework uses the same building blocks: tracks, levels, roles and skills.
Build parallel tracks inside a department, so growing doesn't require managing people. See who holds each role on each level.
Set the level each role expects for every skill in a skills matrix. The same grid is the bar in every team and every promotion case.
Add one or more salary ranges to each role, per currency and location, and export any role as a PDF with its required skills and pay.
Every check-in is pre-filled with the skills the person's role requires and the level expected, so both sides rate against the framework, not against memory.
In practice
Templates
Start each department from its own ladder, then keep the structure consistent across all of them.
Engineering
Five levels from Junior to Principal, across six competencies from shipping code to growing the team.
Engineering
Four levels from Engineering Manager to VP of Engineering, across six management competencies.
Engineering
Four levels from Junior to Staff DevOps Engineer, across six competencies from infrastructure to developer enablement.
Engineering
Four levels from Junior QA to Lead QA Engineer, across six competencies from test design to quality practices.
Product
Five levels from Associate PM to Head of Product, across six competencies from discovery to product strategy.
Data and analytics
Five levels from Junior to Principal Analyst, across seven competencies from framing questions to changing decisions.
Pricing
Plans are priced per organisation, not per seat. Growth is €299 a month for up to 80 people and up to 10 career frameworks; Scale is €499 a month for any number of people and unlimited career frameworks.
Every core feature is on every plan. Paid plans add two things: on Starter, Growth and Scale, notifications can reach people in Slack instead of by email, and on Starter, Growth and Scale, an admin can require Google or Microsoft sign-in for the whole organisation.
€0/month
For small teams putting career levels in writing for the first time.
€149/month
For growing teams ready to formalise their career paths.
Most popular
€299/month
For scaling companies with several teams and departments.
€499/month
For larger organisations that need room to grow.
Every core feature is on every plan. Paid plans add Slack notifications and the option to require Google or Microsoft sign-in; otherwise you pay for plan size — people and career frameworks.
FAQ
Yes. Every department gets its own career framework with its own tracks, levels, roles and skills, edited by the people you assign and published when it is ready. The building blocks are the same everywhere, so every department describes its levels in the same terms, and leadership can line them up side by side.
Yes. A department can hold several tracks side by side — for example an individual-contributor track and a management track — each with its own roles and levels.
Ranges are attached to roles, and roles sit on levels within a track. A role can carry several ranges, per currency and location, and its PDF shows them next to the required skills.
Everyone in your organisation — if you add them, since ranges are optional. In the app they appear on each role beside the people in it; the role's PDF carries the ranges but not the people. Changing them is up to admins and the department's editors. Not ready for pay transparency? Leave them out for now.
Use one skills matrix per framework as the reference for both check-ins and promotion cases. Promotions are proposed with a written rationale and decided by someone above the person who proposed them, so cases can be compared side by side.
There is no automatic import: you rebuild each framework in LadderKit by hand. Most teams use that as the moment to drop the levels and skills nobody actually uses.
How to run an individual-contributor track next to a management track: where the two diverge, how to line up their levels, and how people move between them without losing ground.
Updated 1 October 2026
Five terms that get used interchangeably — career ladder, career framework, competency matrix, job level and grade — untangled, with one department worked through end to end.
Updated 1 October 2026
Start free: build your first department's framework and pilot it with one team, then choose Growth or Scale for the rollout.
Free plan · No credit card required