The Staff Engineer's Path: A Guide for Individual Contributors Navigating Growth and Change

The Staff Engineer's Path is the book I wish existed when I was trying to figure out what staff engineers actually do. Reilly breaks down the role into concrete skills: technical leadership, navigating organizations, setting technical direction, and having impact without authority. The chapter on scope—how to think about problems that span multiple teams or systems—helped me understand why some engineers seem to have more impact than others. The section on writing technical proposals is gold: she shows how to structure arguments, gather feedback, and get buy-in for architectural changes. The book is practical without being prescriptive—she acknowledges that every company defines staff differently, but gives you frameworks to adapt. My only critique is that some sections assume you're at a large tech company, but the principles apply anywhere. I've recommended it to three senior engineers who were considering the staff track, and all of them said it clarified what the role actually entails. Essential reading for anyone trying to understand staff-plus engineering.