Skip to content
all frameworks
04 · Author synthesis

Senior+ Fork

Management track vs IC track
Career fork after Senior EngineerSenior Engineerowns an individual scopeLeadershiptransition / forkManagement trackIllustrative · varies by companyscales impact through peopleand processL1Engineering ManagerL2Engineering DirectorL3VP EngineeringIC trackIllustrative · varies by companycross-team technical leadershiparchitecture · standards · complex problemsL1Staff EngineerL2Principal EngineerL3Distinguished EngineerL4Technical Fellow

After Senior, a career may split into management and IC tracks. In the source diagram, Leadership marks the transition into management rather than a separate grade. The exact steps—Engineering Manager or Director, Staff or Principal—depend on organizational design and do not form a universal ladder.

Management scales impact through people and process. The IC track scales it through cross-team technical leadership, architecture, standards, and difficult problem solving; Staff+ includes several archetypes rather than only Architect.

The fork helps an engineer choose a mode of influence and a company make parallel expectations explicit. Read the level names in the diagram as an illustrative example, not an industry standard.

How to use this model
01

Compare how the person scales impact: through people and process or through cross-team technical leadership.

02

Define expectations across scope, impact, complexity, leadership, and improvement without assuming universal grade names.

03

Build a transition plan around skills, influence, and decision types; take level names from your own organization.

Sources and related materials
Author materials
Share