The Case Against Public Engineering Levels
The article argues against the practice of making software engineering level information (such as junior, senior, staff) publicly visible within companies. It claims public levels create unnecessary status hierarchies, hinder collaboration, and cause anxiety, advocating for a more private and fluid system of career progression instead.
Background
- The article criticizes "public engineering levels" — the practice at large tech companies (Google, Meta, Microsoft, Amazon) of publishing detailed career ladders (e.g., L3, L4, L5) that tie compensation, scope, and promotion criteria to specific titles.
- Proponents argue that transparent levels help job seekers compare roles and negotiate fairly. The author counters that the system primarily benefits employers by rigidly classifying engineers, suppressing wages, and discouraging non-traditional career paths.
- Levels are controversial in tech because they create internal caste systems; engineers often "level-shop" at new companies to jump multiple grades faster than they could internally.
- The essay is part of a broader debate about tech labor markets, pay transparency, and whether software engineering should be treated as a craft or a corporate hierarchy.