This is an incredible book, and I would highly recommend it for anyone who is at all interested in technical leadership at any level.
It focuses very specifically on the challenges of combining technical focus with leadership and/ or management, and steps through roles from hands-on development, through mentoring, tech lead and various levels of engineering manager all the way up to CTO. Along the way, it gives a realistic and well-thought-out sense of what these roles are (and are not), how they differ from lower roles and from subtly different roles at a similar level, and how to succeed at them.
The most interesting thing I took from it though was that the understanding you can gain about the hierarchy of technical leadership roles is useful at all levels, including what we would call "individual contributor" roles (i.e. doing technical work with no direct reports). Engineers at a relatively early stage in their careers can benefit from the first few chapters, which cover what to expect from your own manager, how to start mentoring and how to consider whether long-term you are more interested in management or technical tracks. Equally, having done some low-level management over the last couple of years and now seeking to return to more of a senior technical/ architecture role, I still found the later chapters (about senior tech management roles) fascinating, because I know that even if I never take on those exact roles, understanding the responsibilities and thought processes of those who have them will make me much more effective in working with them and advancing my own ideas.
As an engineer who has stayed in engineering for the last 20 years this book was a read through the many episodes of my career and those of my colleagues. It is a map of non engineering career moves in an engineering career. It moves through many stages, however uncomfortable, an engineer may find themselves in. How to seek out more responsibility, how to just quietly test the water, or jump head first into a more senior role. Too many engineers seem to move in senior positions now that simply haven't put the time in to understand the nuances of business, of people, and of social interaction on all levels. Just because you're an amazing python programmer shouldn't be a promotion to looking after the team. All management should make their engineers read this who aspire to lead, no matter if in projects or with people.
Mandatory reading for any software engineer looking to expand their skill set to include better communication and understanding of how to lead and manage a project/team. This book is immensely useful, and that is regardless of whether moving to the management track is your ultimate goal or not.
Camille is very knowledgeable of all aspects of management within the software industry, and after reading just one page I spent the rest of the book just nodding my head. With sound advice and snippets from others in the industry this book felt well considered.
The way it was written was also very inclusive and engaging.
This is an excellent overview for those considering taking on the challenges of the TL role in a tech environment. I would recommend anyone to read it before their foray into tecn managers to see if their expectations meet their goals.
In my opinion this is an essential read for anyone working (or aspiring to work) within a leadership position within technology. I've been fortunate enough to see Camille present at several conferences, and I always learn something -- whether she is talking about the inner-workings of ZooKeeper, or sharing some the stories of her many successes (and the occasional failure) from leading engineers, she always speaks with authority, humility and compassion.
Over the years I've worked as a tech lead and CTO, and (with hindsight) this is the book that I was missing when I hit several challenges. Camille discusses in depth topics like career planning, establishing mentoring (both unofficial and through line management one-to-ones), creating a culture of feedback (in particular I liked the idea of "skip meetings"), performance reviews, hiring and more.
There are many books about leadership, but if you are a technologist (developer, operator, engineer etc) then Camille's deep technical expertise will most likely speak to you more than books written by her business peers. Camille's experience allows her to empathise with fellow engineers and provide understandable metaphors and analogies that really helped me understand (and debug) some of the more gnarly concepts of leading people.