What I Learned From 'Staff Engineer' by Will Larson
1 min read
The core idea
Staff engineer is a role, not a promotion. The title exists at different companies for different reasons — and understanding which reason applies to your org is essential.
Four common archetypes
| Archetype | Focus |
|---|---|
| Tech Lead | Guides a team through a major initiative |
| Architect | Owns cross-team technical decisions |
| Solver | Drops into hardest problems |
| Right Hand | Extends an executive’s technical reach |
What I took away
The most useful chapter was on writing. Larson argues that writing is the primary leverage mechanism for staff engineers — design docs, strategy memos, postmortems. Code is local. Writing scales.
My notes
- Say no to meetings that aren’t about your highest-leverage work
- Build a “bias for action” — write the doc, share it, iterate
- Your network is your best tool for understanding how the org actually works
What I learned
This book confirmed something I suspected: the staff engineer’s job is 30% technical and 70% communication, judgment, and context. The coding skill is table stakes; the rest is what makes you effective.