Staff Engineer book
What staff engineering is, what archetypes it takes, and how to get there. Half guide, half interview collection.
What staff engineering is, what archetypes it takes, and how to get there. Half guide, half interview collection.
why it matters
The first book to seriously address the 'what is the IC track past senior?' question. Larson's archetype framing (tech lead, architect, solver, right hand) gives you vocabulary for what kind of staff engineer you are or want to be — and helps you stop trying to be all four. The interviews from working staff engineers grounded the abstractions.
key ideas
- Four archetypes: tech lead (one team), architect (cross-team), solver (parachutes into hard problems), right hand (force multiplier for an exec). Most staff engineers do one or two; trying to do all four is the path to burnout.
- Engineering strategy as the staff IC's deliverable — not 'let me code more' but 'let me articulate why we should do X'
- Glue work: the cross-cutting connective work that's invisible to traditional promotion criteria but essential to org function
- Visibility, sponsorship, scope: getting promoted is a separate skill from doing the work
- Trade-offs of going staff: less coding, more meetings, ambiguous deliverables. Decide whether this fits.
memorable framings
- 'Staff engineers do less and less of what they got hired to do.'
- 'You're not paid to write code; you're paid to make the company succeed.'
who should read it
Senior engineers asking 'what's next?' Read with The Staff Engineer's Path (Reilly) — they complement each other.