The Staff Engineer's Path book
Practical guide to the day-to-day of staff IC work — locating yourself, the work, leading projects without authority.
Practical guide to the day-to-day of staff IC work — locating yourself, the work, leading projects without authority.
why it matters
Where Larson's *Staff Engineer* is about defining the role, Reilly's book is about doing it. The 'three big things' (big-picture thinking, project leadership, leveling up the org) gives a clearer execution model than the archetype framing. The chapter on 'glue work' alone is worth the book.
key ideas
- Three pillars: big-picture thinking, leading projects without authority, leveling up the org
- Locating yourself: understand your scope, your peers, your stakeholders, your superpowers, before deciding what to work on
- Maps and treasure maps: tools for orienting yourself and others in a large org
- Project leadership without people-management authority requires writing, alignment, and relentless follow-up
- Glue work is a load-bearing organizational function and shouldn't be invisible — make it legible to your management chain
memorable framings
- 'You can't be senior in a vacuum.'
- 'The job of a staff engineer is to be useful.'
who should read it
Pair with Larson's *Staff Engineer*. Reilly's chapters on writing and project leadership are the most practical staff-IC content I've read.