Career Progression Frameworks: How to Read Yours (and What to Do Without One)

A career progression framework is a document that tells you what the next level looks like — the skills, behaviors, and scope you need to demonstrate to get there. Some companies publish theirs. Most do not. And even when a framework exists, most people either have not read it or have read it without knowing how to use it. This is a guide to reading the framework if you have one, building one if you do not, and in both cases, turning it into a set of evidence checks you can run against your own career journal.

What a career progression framework actually is

A career progression framework — also called a career ladder, leveling rubric, or competency matrix — is a document that describes what each level in a role looks like. It names the skills, behaviors, scope, and impact expected at each stage, from entry-level through senior leadership. In theory, it removes ambiguity from promotions: if you demonstrate the behaviors at the next level consistently, you get promoted to that level. In practice, it is one input among several, including budget, headcount, timing, and calibration politics — but it is the only input you can control.

Frameworks come in two shapes. Ladders are vertical: junior, mid, senior, staff, principal, each defined by increasing scope and judgment. Lattices allow horizontal movement: an IC might move into management, then back to IC, or shift from engineering into product. The shape matters because it determines whether your next move is up, across, or both — and the evidence you need changes accordingly.

How to read a career progression framework

Most people read a framework the wrong way. They scan their current level, confirm they are doing those things, and assume the promotion will follow. The framework's value is not in confirming your current level — it is in defining the gap between where you are and where you want to be.

• Read your target level, not your current level. The behaviors described at the next level are the evidence you need to collect. Your current level's description is a checklist you have presumably already passed.
• Identify the 2-3 dimensions that change most between levels. In many frameworks, the jump from mid to senior is about scope (owning a system vs. owning a task). The jump from senior to staff is about judgment (making decisions with incomplete information). The jump from staff to principal is about leverage (creating outcomes through others). Name the specific shift your jump requires.
• Look for the verbs. 'Contributes to' at one level becomes 'leads' at the next becomes 'defines' at the one after that. The verb progression tells you what kind of evidence the calibration committee will look for.
• Note what is absent. Many frameworks describe what strong performance looks like but not what mediocre performance looks like. The absence is your risk zone — the behaviors you might be doing at your current level that you mistake for next-level performance.

What to do when your company has no framework

Many companies — especially startups, mid-stage companies, and non-tech organizations — have no published framework. The absence does not mean levels are arbitrary. It means the criteria are implicit, which is worse: you cannot close a gap you cannot see.

Build your own rubric. It takes an hour and changes how you think about your career for the next two years.

• Borrow a public framework. Dropbox, GitLab, Levels.fyi, and others publish their engineering, product, and design ladders. Find the one closest to your role and company size. It will not be exact, but it will be close enough to define the target.
• Interview people at the level above you. Ask three questions: what are you responsible for that you were not responsible for at the previous level? What skill mattered most in your promotion case? What surprised you about the expectations at this level? Three conversations produce a usable rubric.
• Write the rubric as 5-8 dimensions with a one-sentence description of what 'good' looks like at your target level. This becomes the scorecard you run your evidence against quarterly.
• Validate with your manager. Share the rubric and ask: 'Does this match what the company looks for at the next level?' Your manager will correct the dimensions that are wrong and confirm the ones that are right. Now you have a framework.

IC track vs. management track

The most consequential question a framework answers is whether your next move is up the IC ladder or across to the management track. They are different roles, not different ranks. A staff engineer and an engineering manager are peers, not a hierarchy — and the skills that make you excellent at one do not automatically transfer to the other.

The IC track rewards deepening: system design, technical judgment, mentoring, and architectural influence. The management track rewards broadening: hiring, team performance, organizational design, and stakeholder management. If your journal entries cluster around mentoring and cross-team coordination, that is a signal worth examining. If they cluster around deep technical work and system design, that is a different signal. Neither is better. But picking the wrong track wastes years of evidence collection.

Turn the framework into evidence checks

A framework on a wiki page does nothing for your career. A framework turned into evidence checks runs your career. For each dimension at your target level, ask: do I have dated, specific examples of this behavior from the last six months? If yes, you are building the case. If no, you have identified the gap — and the gap is actionable.

• For each framework dimension, create a journal tag or category. Every time you produce evidence at the target level, capture it under that tag.
• Run the evidence check quarterly. Count the examples per dimension. Dimensions with zero examples are the gaps; dimensions with four or more are strengths. This is your skills gap analysis, derived directly from the framework.
• Bring the check to your 1:1. 'Here are the dimensions I have strong evidence for. Here are the gaps. What projects or opportunities would help me build evidence in the gap areas?' This question gives your manager something concrete to work with.

Common mistakes when using career frameworks

• Treating the framework as a checklist instead of a measurement tool. Checking boxes is not the same as demonstrating consistent behavior. Calibration committees look for patterns across months, not isolated incidents.
• Optimizing for every dimension equally. Not all dimensions carry equal weight. Identify the 2-3 that are most differentiating at your target level and build disproportionate evidence there.
• Assuming the framework is the whole picture. Budget, headcount, timing, and calibration dynamics also affect promotions. The framework defines the evidence you control; it does not guarantee the outcome.
• Comparing against peers instead of the rubric. Your peer's strength in one dimension does not mean you are weak in it. Score against the framework language, not the room.
• Reading the framework once and never returning to it. Companies update frameworks, and your understanding of the dimensions deepens as you accumulate evidence. Re-read quarterly alongside your evidence check.

A framework is a measuring instrument, not a career strategy. It tells you the shape of the target; it does not tell you how to hit it. Use it to define the evidence you need, check quarterly whether you are collecting that evidence, and bring the gaps to your manager as specific questions rather than vague ambitions. That is the entire playbook.