The Software Engineer's Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startups

The author traces a consistent path, from describing the industry landscape, then the roles and he brings the reader naturally into the senior engineer landscape and cross team collaboration. Plenty of useful tips, albeit some are obvious, along the way that every engineer should keep in mind during their growth. I found the advice practical and actionable, and adds suggestions even at senior levels to expand knowlege and foster collaboration.

is very good book written from a very experienced person which i followed him for years in LinkedIn, very useful to ready it when you start your career in junior and mid level. The only negative is the material of the book is not in a great quality for the price that you pay.

I've just finished reading Gergely Orosz's book "The Software Engineer's Guidebook". I think it may be required reading for Software Engineers.The book addresses many of the career and role questions that Software Engineers will ask their managers or mentors. Topics such as...- How can I succeed as a Software Engineer?- What's the difference between being Senior and Staff/Principal?- What does it mean to be a Tech Lead, and how do you succeed as one?The book covers a lot of topics, so it doesn't always go into a ton of detail, but it gives the reader plenty of help/tips/guidance.I recognised and agreed with all of it, and reminded myself of a few things I should be doing better at. I suspect I'll dip into this book in the future, and quote from it when mentoring others.

As a senior level software engineer I found myself enjoying this book, but only up until midway through. After that it kind of got repetitive and stopped being enjoyable