A critique of Will Larson's widely-cited 'staff engineer archetypes' framework as practical career advice. The author argues that targeting a specific archetype (tech lead, architect, solver, right hand) is misguided because these roles emerge organically from building trust and delivering value over time — not from consciously aiming at them. The core thesis is that a staff engineer's defining trait is being genuinely useful to the company and accepting accountability for outcomes they don't fully control. Rather than picking an archetype to emulate, engineers should focus on consistently delivering value, understanding their manager's real priorities, and building deep organizational trust. The archetypes are better understood as anthropological descriptions of how staff engineers can be useful once trust is established, not a roadmap for getting there.
6 Comments
Sort: