career-leveling

# Career Leveling ## Why Frameworks Matter A career framework is foundational infrastructure. Comp bands, performance ratings, hiring decisions, and promotion processes all anchor to it. A vague or absent framework leaves bias and politics to fill the void. ## Core Principles 1. **Impact over tenure**: levels reflect the work, not the years 2. **IC parity with management**: senior IC track runs as long as management track 3. **Specific behavioral anchors**: every dimension at every level 4. **Same framework across the company**: vary the dimensions by function, not the principles 5. **Calibrated promotions**: panel reviewed; not single-manager whim ## Level Dimensions Typical 4–7 dimensions: - **Scope**: project → team → org → company → industry - **Ambiguity**: defined tasks → defined goals → undefined problems - **Leadership**: self → mentors → leads → builds teams → builds leaders - **Technical / functional depth**: junior → competent → senior → expert → authority - **Business acumen**: task-aware → context-aware → strategy-aware → strategy-shaping - **Communication / influence**: team → cross-team → org → industry Each level defines expected behavior across each dimension. Anchored in observable behavior — not adjectives like "proactive" or "results-oriented." ## Typical Engineering Level Structure | Level | Title | Scope | Leadership | |-------|-------|-------|------------| | L1 | Engineer I | Tasks within a project | Self | | L2 | Engineer II | Owns features | Informal mentor | | L3 | Senior Engineer | Owns systems within a team | Mentors others; sometimes tech lead | | L4 | Staff Engineer | Cross-team scope | Multiplies a team or function | | L5 | Senior Staff / Principal | Org-wide scope | Multiplies an organization | | L6 | Distinguished | Company-wide impact | Influences company direction | | L7+ | Fellow / VP IC | Industry impact | Defines technical strategy | The IC ladder runs as long as the management ladder. Both reach Director-, VP-, and SVP-equivalent compensation. ## Promotion Process ### Manager-Nominated, Calibrated 1. Manager identifies candidate as ready (often through 1:1 conversations and growth tracking) 2. Manager writes a packet: evidence against next-level rubric (specific examples) 3. Skip-level reviews 4. Calibration panel of cross-functional senior leaders reviews 5. Decision: promote, defer, or specific gap to close ### Promotion Packet Template - Candidate name, current level, proposed level - Evidence per dimension (specific examples, observable behavior) - Cross-team impact examples - Manager recommendation - Outstanding questions ### Slot-Based vs. Open - **Slot-based**: fixed promotions per cycle. Reduces inflation; creates zero-sum dynamics. - **Open**: anyone meeting bar promotes. Better default; monitor distribution. ### Time-at-Level Minimums Avoid as hard rules. Strong performers should be promoteable when their work demonstrates next-level scope, not at year-N. Use "performing at next level for 6+ months" as the test. ## IC Track Parity (Critical) Common failure: IC ceiling at mid-senior, talented ICs forced into management or out. Counters: - Define IC track as long as management track - Same titles confer same comp at parallel levels - Senior IC roles have organizational impact comparable to senior managers - Movement between tracks supported, not penalized - Senior leaders publicly celebrate senior IC trajectories ## Common Failures - No framework: managers level intuitively; high variance by manager and demographic - Tenure-based progression: years equal levels - Vague rubrics: "demonstrates leadership" without anchors - IC ceiling: no growth past mid-senior IC - Manager tax: managers promoted faster than equivalent ICs - Solo-manager promotion decisions: variance and bias - Promotion politics: roles created to retain; titles without rubric backing - Framework launched without comp linkage: levels exist on paper, comp doesn't follow ## Migrating to a Framework When introducing or fixing: 1. Don't retrofit perfectly — declare a "leveling moment" with explicit re-leveling 2. Run parallel: managers propose; calibration reviews; anomalies surface 3. Acknowledge some levels will be wrong; commit to fixing next cycle 4. Tie comp bands to the new framework 5. Communicate transparently 6. Audit by demographic for disparate impact ## Promotion Equity Audit: - Promotion rates by demographic - Time-in-level by demographic - Manager pattern (who promotes faster) - Calibration outcomes by demographic Common pattern: women and Black employees often have longer time-in-level than white men with comparable performance. Calibration is the intervention. ## Cross-References - `career-framework-architect` agent - `performance-management-systems` skill - `pay-bands-market-data` skill - `dei-strategist` agent ## Key References - Bock, L. (2015). *Work Rules!* - Fournier, C. (2017). *The Manager's Path*. - Larson, W. (2021). *Staff Engineer*. - Public engineering ladders (e.g., GitLab, CircleCI, Patreon — published online)