Guide

Pick a public framework and grade yourself with evidence, not vibes. Dropbox's Engineering Career Framework is explicit enough to use as a mirror. progression.fyi collects many others.

The exercise takes about 20 minutes on paper. Do it before you argue for a level in a 1:1 or an interview.

Concept

Score work on the four axes. Calibration committees (see promotion) look for a pattern, not a peak. One heroic week does not move a level.

Walking through the exercise

  1. Choose one level description at your claimed level and one at the next level (for example Dropbox IC2 vs IC3, or your company's SDE2 vs SDE3).
  2. List three pieces of work from the last six months (projects, incidents, designs, reviews).
  3. For each piece, score the four axes 1–4.
  4. Mark which next-level behaviors you already show consistently, which you show once, and which you have never practiced.
ScoreScopeAutonomyComplexityInfluence
1Single ticketSteps providedLocal changeOwn PR
2Feature sliceHow mostly clearOne service, known patternsTeam reviews
3Feature / small project end to endYou clarify howCross-cutting or careful migrationTeam direction in an area
4Multi-quarter / multi-teamAmbiguous problemHard novel or high-risk systemsPeer teams / org practices

Example

Last quarter you "owned dark mode." Axis scores: scope 2 (UI surface, one app), autonomy 2 (PM had mocks), complexity 2, influence 2 (your team). That is solid mid-level delivery. A senior-shaped version: lead accessibility and theming as a platform concern across three apps, propose a shared token system, negotiate rollout with design, and leave docs so other teams adopt it — scope 3–4, autonomy 3, influence 3.

Interview loops often probe the level below and at the one you want. Behavioral rounds especially: they are listening for autonomy and influence, not only technical correctness. Pair this with behavioral interviews when you prepare stories.

On a healthy team, you should be able to answer: What level am I hired at, what does the next level look like here in writing, and what evidence would convince my manager? Keep a running doc of evidence mapped to the axes so promotion is not a scramble.

Common mistakes

  • Grading on vibes. "I feel senior" is not a packet.
  • Using one peak. A single incident save is a story; a year of closing loops is a level.
  • Skipping the next-level column. You need to see which behaviors you have never practiced.

Check yourself

You have one dramatic on-call save and a year of well-scoped tickets. What does a calibration committee see?

A peak plus a mid-level pattern. The peak does not move the level by itself.

You cannot find a written ladder at your company. What do you do?

Use Dropbox or another public framework as a stand-in and align with your manager in a 1:1.

Key takeaways

  • Self-assess with a public ladder and evidence from recent work, scored on the four axes.
  • Mark consistent / once / never — consistency is the bar.
  • Keep artifacts so the packet is not a scramble.
  • Interviews probe the same axes. Stories should too.

Further learning

Dropbox Engineering Career Frameworkdropbox.github.io progression.fyi — career frameworks collectionCareerminds helps organizations build clear, scalable job architecture that boosts engagement and retention. Empower employees with visible growth paths, skill progression, and our ready-to-use templates.Careerminds

Back to the map: what the levels mean.