Path to Senior Engineer Handbook

What is inside

The repository is a single, well-organised README of links, grouped by format and topic:

• Newsletters: general engineer growth, staying up to date, system design, reliability engineering, leadership and web development
• Books: communication and writing, storytelling, career growth and promotions, software design, system design and leadership
• Courses, papers, YouTube channels and podcasts
• Communities, LinkedIn creators, platforms and helpful tools
• Other catalogues of similar resources

It had about 18,300 stars and 1,700 forks on GitHub as of September 2026 and was still being updated that month, under the MIT licence.

Why it is useful

Most learning lists for engineers are about technical skills. This one gives unusual weight to communication, relationships, writing, feedback and influence: books such as Crucial Conversations, Thanks for the Feedback and The Manager's Path sit next to A Philosophy of Software Design and The Staff Engineer's Path. That reflects what actually changes between mid-level and senior roles, where the difference is often scope, ownership and how well you work with others rather than raw coding ability.

Where it falls short

• It is a list, not a guide. There is no ordering, level or explanation of why each item matters. Faced with dozens of newsletters and books, it is easy to subscribe to everything and read nothing.
• Quality varies. Some links are classics; others are newer newsletters of mixed depth.
• No context on your situation. It will not tell you which gap you have. For that you need honest feedback from a manager or mentor, or a framework such as an engineering ladder.

How to use it without drowning

1. Name your gap first. Ask your manager or a senior colleague what would make you clearly senior. Common answers: owning larger projects, writing clearer proposals, handling disagreement, mentoring.
2. Pick one book from the matching section and read it properly, applying one idea each week.
3. Choose at most two newsletters and unsubscribe from anything you do not open for a month.
4. Revisit the list every few months when your gap changes.

A reasonable starting set for many engineers: one communication book, The Software Engineer's Guidebook for the career map, and one design book such as A Philosophy of Software Design.

Common questions

Is it for students? Parts are useful early (communication, writing), but most of it assumes you already have a job. Students gain more from building projects and technical fundamentals first.

Do I need to read everything? No. Treat it like a library catalogue, not a curriculum.

Is it kept up to date? Yes, as of September 2026 it was receiving updates.

Best for: mid-level engineers who want to reach senior and need a starting point for the non-technical skills that level requires.