
A ladder is useful. It is not enough.
Titles create clarity, but they also hide important differences. Two engineers at the same title can have completely different strengths: one may be a deep builder, another a systems owner, another a force multiplier. The map makes those differences visible.The Old Model: One Upward
Path
Clear, But Narrow. It Turns Growth Into A Title Chase And Forces Everyone Into The Same Definition Of Progress.
Good For Compensation Bands And HR Structure.
Weak For Understanding Real Engineering Strengths.
Often Rewards Visibility Before Mastery.
The Better Model: A Role Ladder Plus A Growth Map
The Ladder Stays As The Floor. The Map Shows How You Actually Grow: Deeper, Wider, Sharper, Or More Influential.
Useful For Hiring, Reviews, Mentorship, And Project Allocation.
Rewards Genuine Spikes Instead Of Fake Balance.
Makes The Next Improvement Obvious.
What we actually mean.
These are written to be discussable. A good candidate should be able to defend their rating with examples from real work: trade-offs made, systems shipped, incidents handled, people unblocked, and decisions communicated.Axis 01
Technology
Depth in the stack, architecture, debugging, performance, and technical judgment. This comes directly from the ladder's Technology axis.
Level five looks like
Sets technical direction, guides adoption, and defines the long-term technical path.
Axis 02
Project Ownership
How much of the project outcome you carry: from understanding the work, to owning modules, to evolving entire systems.
Level five looks like
Owns the strategic portfolio of projects and their alignment with business goals.
Axis 03
People Management
How much you grow, mentor, and manage others — from collaborating well to developing teams and leaders.
Level five looks like
Builds leaders, shapes culture, and develops the technical organisation.
Axis 04
Process Improvement
How seriously you improve the way work gets done: delivery process, standards, reliability, and team discipline.
Level five looks like
Defines scalable processes and the strategic direction for how engineering operates.
Axis 05
Influence
The reach of your impact: from your own work, to the team, to the company and external forums.
Level five looks like
Drives company-wide technical direction and represents the organisation externally.
Axis 06
Soft & Communication Skills
How clearly you communicate ideas, align people, and represent technology in discussions, reviews, and stakeholder conversations.
Level five looks like
Acts as a trusted technical voice for senior stakeholders, partners, and high-stakes decisions.
The ladder still exists.
Transparency needs a ladder. Growth needs a map. The roles below are not meant to flatten people into one number; they show the broad expectations that usually come with each level.Role fingerprints
Each role has a different shape across the same six axes used everywhere on this page: Technology, Project Ownership, People Management, Process Improvement, Influence, and Soft & Communication Skills.
Intern
Absorbs fundamentals and ships with support.
SDE 1
Delivers scoped tasks with improving discipline.
SDE 2
Owns features and explains trade-offs clearly.
SDE 3
Leads modules, decisions, and delivery quality.
Senior SDE
Has strong craft and owns meaningful systems.
Tech Lead
Creates leverage through architecture and team direction.
Head of Eng
Scales teams, standards, delivery, and engineering culture.
CTO
Owns technology direction, business fit, and long-term leverage.
Important: this is a calibration tool, not a compensation promise. Real level decisions depend on project complexity, consistency, business impact, and live discussion quality.
Rate yourself across six dimensions.
Use this as a conversation starter, not a certificate. The goal is not to claim you are a perfect engineer. The goal is to understand your strongest spike and the next axis worth improving.Technology
Depth in the stack, architecture, debugging, performance, and technical judgment. This comes directly from the ladder's Technology axis.
Project Ownership
How much of the project outcome you carry: from understanding the work, to owning modules, to evolving entire systems.
People Management
How much you grow, mentor, and manage others — from collaborating well to developing teams and leaders.
Process Improvement
How seriously you improve the way work gets done: delivery process, standards, reliability, and team discipline.
Influence
The reach of your impact: from your own work, to the team, to the company and external forums.
Soft & Communication Skills
How clearly you communicate ideas, align people, and represent technology in discussions, reviews, and stakeholder conversations.
Live Result
Your engineering shape
Your shape reads as
Still climbing
You are building range, but no single axis has become a spike yet. That is not a failure; it simply means your next move should be depth, not more surface area.
Next best move: protect your spike in Technology, then raise Technology by one level with a concrete project or habit.
From page to conversation.
This should make interviews and reviews less vague. Instead of asking whether someone is “senior enough,” we can talk about the axes that matter for the role.Self-assessment
You plot your current shape and identify your strongest spike. We care more about evidence than self-rating.
Evidence discussion
We test the rating through real examples: architecture decisions, ownership moments, trade-offs, incidents, mentoring, and communication.
Project fit
We map the person to the work. Deep builders need hard systems. Multipliers need team leverage. Owners need whole outcomes.

