You just became an engineering manager, and your first quarter is the one that sets the tone. You will not have time to read a shelf of books, so the question is not "what is good," it is "what will actually help in the next 90 days."
This is a shortlist, ordered by when it helps most. It overlaps with our longer list of books an engineering manager should read, but here the goal is narrower: get through your first three months without dropping the ball. Think of the longer list as a career reading plan and this one as triage for the quarter in front of you.
Read these in week one
1. The Manager's Path, by Camille Fournier
The closest thing to a map of the whole job. Fournier walks the path from mentoring one person to running an organization, and the early chapters mirror exactly where you are now. Read the sections one level above and one level below your role first. It is the fastest way to understand what your manager expects and what your reports need.
2. The Making of a Manager, by Julie Zhuo
Written for the exact moment you are in: the shift from doing the work to being responsible for it. Zhuo is honest about the awkward early days, the impostor feeling, and the small habits that build trust. It is short and kind, and it will calm you down in the first week.
3. The First 90 Days, by Michael Watkins
Not written for engineering, and that is fine. It is the standard playbook for any leadership transition: learn before you change things, secure early wins, and match your strategy to the situation you inherited. Skim it for the transition framework, then come back to it before any bigger role change later.
Read these in month one
4. Radical Candor, by Kim Scott
The core idea is simple and hard: care personally and challenge directly, at the same time. Most new managers fail on the second half because they are afraid of being disliked. Scott gives you a way to give clear feedback without being harsh, which is the single most useful skill in your first quarter.
5. The Coaching Habit, by Michael Bungay Stanier
A thin book with one big lesson: ask more, tell less. New managers rush to give answers because it is what made them good engineers. This book teaches a handful of questions that turn your one-on-ones from status updates into real conversations. You can read it in an evening and use it the next morning.
6. Resilient Management, by Lara Hogan
Practical and specific to tech teams. Hogan covers the mechanics most books skip: running a useful one-on-one, understanding what motivates each person, and having the hard conversation before it becomes a crisis. Keep it near your desk and use it as a reference, not a cover-to-cover read.
Read these by month three
7. An Elegant Puzzle, by Will Larson
Once the people basics settle, you will start hitting systems problems: team sizing, on-call load, technical debt, how work flows. Larson treats these as design problems with real trade-offs. Read it when you are ready to think about the shape of your team, not just the individuals in it.
8. Become an Effective Software Engineering Manager, by James Stanier
A hands-on manual for the software EM specifically. It goes deep on the day-to-day: running meetings, managing up, handling delivery, and building your own operating routines. It is the book to reach for when you want concrete process rather than philosophy.
9. High Output Management, by Andrew Grove
The oldest book here and still one of the sharpest. Grove, who ran Intel, frames a manager's job around output: your output is the output of your team plus the teams you influence. The chapters on meetings and on where a manager's real influence comes from will reframe how you spend your time. Save it for month three, when you have enough context for it to land. It reads like it was written last year, which tells you how little the core of the job has changed even as the tools around it have.
How to actually get through them
You will not finish nine books in 90 days, and you should not try. Read the two or three that match your weakest area first, use the rest as references, and let real problems pull you back to the right chapter. A book you half-read at the right moment beats one you finished at the wrong one.
A rough plan that works: pick one book from each group. From week one, read the one that matches how you are feeling, whether that is lost about the role or nervous about the shift. From month one, read the feedback or coaching book, because you will have a hard conversation coming whether you feel ready or not. Leave the systems books for when the day-to-day is no longer on fire. Match the book to the problem in front of you, and the reading will stick because you can use it the same week.
Two habits make any of these worth more. Keep a running note of the ideas you actually tried, and what happened. And talk about them with one other new manager, even informally. A book gives you the language; a peer tells you whether you are using it right. If your company runs a manager cohort or a mentor program, that is the place to compare notes.
One thing no book will fix: the gap that opens when you go off for a few days and the questions pile up for whoever is standing in. Coverage is a skill you build, not a book you read. StandIn helps with the small version of it: you write one short brief at the end of your day, and while you are away it answers your team from what you wrote, with a source under each answer, and it says so when the answer is not there. The reading makes you a better manager. Writing things down clearly is what lets the team keep moving when you step away.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.