Engineering career frameworks get airtime
Threads on X have been circulating a detailed Engineering Career Framework that maps expectations from SE1 up to VP, stresses separate IC and management tracks, and notes that roles like SE3 can be long‑term positions. The discussion—amplified by experienced leaders sharing org‑design notes—restarted debate about clear timelines and promotion criteria in tech organisations. Those conversations matter because codified frameworks shape both career expectations and how engineering leaders prioritise cross‑functional influence. (x.com, x.com)
A software engineering career framework is a company’s map for what “good” looks like at each level, the same way a school syllabus spells out what Algebra I covers before Algebra II. The recent X threads took off because they showed that map in unusually concrete detail, from entry-level engineer to vice president, instead of leaving promotion standards to manager folklore. (github.com, x.com) The framework that circulated most widely was Jorge Fioranelli’s open-source “engineeringladders” project, which has about 8,500 GitHub stars and splits engineering into four ladders: developer, tech lead, technical program manager, and engineering manager. It also scores roles across five axes — technology, system, people, process, and influence — so a level is defined by scope, not just by years worked. (github.com) That structure cuts against one of tech’s oldest assumptions: that the only way “up” after senior engineer is to manage people. LeadDev’s 2022 guide says many engineers leave when opportunities are not clearly defined, especially when senior individual contributor roles are missing or invisible. (leaddev.com) The separate individual contributor track matters because it treats technical leadership like architecture, not like a consolation prize for people who do not want direct reports. Will Larson’s Staff Engineer project describes staff engineer as a branch that usually opens after senior software engineer, often five to eight years into a career, with impact coming through technical direction rather than line management. (staffeng.com) One reason the X discussion spread is that the shared framework says some levels are destinations, not waiting rooms. In Fioranelli’s ladder, “Senior Developer” starts at level 4, and the model explicitly notes that each company should adapt titles and expectations rather than assume every engineer must keep climbing forever. (github.com) That idea sounds small until you compare it with how many companies actually run promotions. LeadDev wrote in 2023 that without a shared framework, different managers end up with different definitions of what “good” means, which turns calibration and promotion reviews into arguments over vibes instead of evidence. (leaddev.com) A framework also changes hiring because it turns a title into a checklist. LeadDev’s 2020 piece calls an engineering ladder an “objective yardstick” for hiring rubrics, onboarding, performance reviews, and compensation, which means the same document can shape who gets hired, who gets promoted, and how pay bands are defended. (leaddev.com) That is why experienced leaders jumped into the thread with org-design notes instead of just career advice. If a company says a mid-level engineer owns a feature, a senior engineer shapes a team, and a staff engineer influences multiple teams, then headcount planning, team composition, and promotion packets all start using the same ruler. (leaddev.com, progression.fyi) The sharpest debate is not whether frameworks help, but how rigid they should be. LeadDev warns that frameworks should reduce ambiguity and bias, but they also need to evolve as the company changes, because a 20-person engineering org and a 2,000-person engineering org do not need the same scope at the same title. (leaddev.com, leaddev.com) So the X threads were really about a power shift inside engineering organizations. Once expectations are written down in public, “not ready yet” has to compete with a document that names the behaviors, the scope, and the level where an engineer can stay excellent for years without becoming a manager. (x.com, github.com, leaddev.com)
