You have no manager, but you have no direct reports. You have influence, but no authority. Orosz interviews real Staff+ engineers from Uber, Stripe, and Google to show you how to lead without a title.
Perhaps the most painful chapter is on Visibility . Senior engineers often do vital work (refactoring, reducing tech debt, fixing monitoring) that management doesn't see. Orosz provides scripts and frameworks for making the invisible visible without sounding like a self-promoting jerk. The Software Engineer-s Guidebook
I have about 50 highlights, but here are the three concepts that fundamentally changed how I view my job. You have no manager, but you have no direct reports
You know how to code, but you don't know how to get promoted. This book breaks down the behavioral differences between a Level 2 and a Senior. It’s not about writing faster; it’s about unblocking others. Perhaps the most painful chapter is on Visibility
It is practical, cynical in the right places (he acknowledges that politics exist), and optimistic about the craft.
Don’t let the title fool you. This isn't just for Junior devs.
The One Book Every Senior+ Engineer Should Read: A Review of “The Software Engineer’s Guidebook”