Engineering
Software Engineer
Five levels from Junior to Principal, across six competencies from shipping code to growing the team.
- 5 levels
- 6 competencies
Career ladders
Describe how people grow in each department — the tracks, the levels and the roles on them — and publish it when it is ready for everyone to read.
Free plan · No credit card required
How it works
Add tracks side by side — an individual-contributor track next to a management track — and put a role on each level. Drag roles between levels as the picture changes.
Attach skills to the framework and set the level every role expects. That grid is the skills matrix, and it is what check-ins and promotion cases are measured against.
Admins and the department's editors assign each person the role they hold today. Their profile shows the role, how long they have held it, and the roles before it.
When the framework is ready, publish it. Everyone in the organisation can then read it and open any role to see what it asks for.
Permissions
Good to know
Keep exploring
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.
Product
Five levels from Associate PM to Head of Product, across six competencies from discovery to product strategy.
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.
For startups
For founders of 10–60-person startups setting up levels, their first managers and fair promotions.
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
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
FAQ
In LadderKit a career framework is everything one department describes — its tracks, levels, roles and the skills each role needs. A career ladder is one track inside it: the sequence of roles someone can climb.
Only admins and the department's editors. Everyone else in the organisation sees it once it is published.
An admin or one of the department's editors assigns the new role, and the previous assignment closes automatically. For a step up, the promotions workflow adds a proposal and a decision before the change.
Yes — editors keep working on it and changes show straight away. Check-ins already started are unaffected: each one keeps a snapshot, taken when it started, of the skills and levels it is assessed against.
Yes. Drafts count exactly like published departments, so the limit cannot be sidestepped by keeping frameworks unpublished. Deleting a department frees its place.
Start free with one department and publish it once the levels feel right.
Free plan · No credit card required