A Simple Approach to Career Growth
Making career conversations clearer and more useful
One question exposes the weakness in a lot of engineering organizations:
What do I need to do to get to the next level?
Too often, nobody can answer it clearly.
Not because people do not care.
Because the team has never agreed on a fair, shared way to evaluate growth and at the same time, bringing a framework could feel like too much.
The real issue
Performance reviews influence promotions, compensation, and scope. But in many teams, those decisions still come down to memory, interpretation, and whoever can argue most confidently in calibration. A fairer system needs shared expectations, observable behaviors, and decisions backed by evidence rather than intuition alone.
This is not really a people problem.
It is a system problem.
What a framework does
A good framework gives everyone the same map. It creates shared language for what strong performance looks like and helps managers apply expectations more consistently across teams.
At a minimum, it should do three things:
Define the key dimensions of the job.
Show how expectations grow with seniority.
Anchor those expectations with concrete examples.
One of the first career matrices I came across was CircleCI’s, which greatly inspired me to invest more in that path.
Make growth explicit
Words like “ownership,” “impact,” or “leadership” sound useful until everyone means something different by them.
A better framework makes those ideas specific. Instead of saying someone “shows ownership,” it describes what that looks like at different levels, from handling their own work reliably to driving outcomes through ambiguity and creating accountability across a wider group. Clear progression criteria make career conversations more actionable and more fair.
Shared language matters
When managers and engineers use the same framework, conversations get better fast.
Instead of:
“I think I’m doing well.”
You get:
“I’m strong here.”
“This is where I’m still developing.”
“This is the gap to the next level.”
That kind of clarity matters because competency frameworks are most useful when they create a common understanding of what is expected and what behaviors are valued.
Fairness needs evidence
The strongest frameworks are not just descriptive. They help teams make fairer decisions.
That means:
Using concrete examples, not vague impressions.
Reviewing people against the same expectations.
Calibrating across managers to reduce inconsistency and bias.
Documenting reasoning clearly enough that others can challenge it.
This is one of the most useful ideas in the manager guidance you shared: decisions are better when they are evidence-driven, reviewed by multiple people, and based on what someone consistently demonstrates rather than on isolated moments or personal affinity.
Growth is not only promotion
One helpful distinction is separating growth within a level from promotion to the next one.
A simple model like:
Learning
Matching
Mastering
can make progress visible without forcing every development conversation into a title change. That kind of structure helps people see that growth is continuous, even when promotion is not immediate.
Why this matters
Without a clear system, the same problems keep showing up.
Strong people get vague feedback.
Promotions feel subjective.
Managers rely too much on instinct.
Engineers are left guessing what actually matters.
Over time, people do not just lose motivation. They lose trust in the process.
Where Levell comes in
That belief is what led me to build Levell.
The goal is simple: make performance evaluations more consistent, evidence-based, and fair, without turning them into a bureaucratic exercise.
I initially built this for myself, and then decided to share it with others. I believe that a minimalist framework that focuses exclusively on assessments and framework definition has great value.
Start smaller
You do not need a huge framework to improve this.
Start with one or two competencies. Define what they mean at different levels. Use real examples. Then bring that language into your next review cycle.
That alone can make performance conversations clearer, more useful, and more fair.