The Staff Engineer's Path

The most practical book I know on what the staff engineer role actually involves.

What it's about

Tanya Reilly describes the staff engineer role through three pillars: big-picture thinking, project execution, and leveling up the engineers around you. Rather than a job description, the book is a set of habits for each, from understanding the organisation you work in to getting a stalled project moving to raising the standard of a whole group.

What stuck

Maps before moves. The book asks you to build a picture of where you are: the organisation's structure, its unwritten rules, where the real decisions happen, and where things are headed. Choosing work without that picture is how smart people end up busy on the wrong problems.

Choosing the problem is the job. At this level, the scarcest resource is attention, yours and your team's. Picking which problems deserve a team, and which should be explicitly left alone, matters more than solving any one of them brilliantly.

Execution includes the unglamorous parts. Driving alignment, writing the document nobody wants to write, noticing a project is drifting and saying so early. This is real engineering work, and the book treats it that way.

Leveling up scales further than code. Reviews, mentoring, and setting standards that make good work the default reach more of the codebase than anything one person can write.

What I'd apply

• Keep a written map of the systems and teams I work across, and revisit it each quarter.
• Say no more deliberately: every "yes" to a side quest is a "no" to something on the map.
• Treat design reviews and mentoring as deliverables, not interruptions.