Tech Lead guides
Guides for Tech Leads
The Tech Lead role, the move into it and the day-to-day, explained through the book’s 60 principles.
These guides answer the questions people ask before and during the move into the role. How you become a Tech Lead, how it differs from an Engineering Manager, what you are accountable for day to day. Each section links to the principles from the book that go deeper.
Career guide
How to become a Tech Lead: the transition guide
You become a Tech Lead the day you are accountable for what the team ships, and no longer only for your own code.
5 FAQ, 22 related principles
Read the guide →
Roles guide
Tech Lead vs Engineering Manager: what’s the difference?
The Tech Lead is accountable for a team’s technical direction: architecture, quality, technical choices, delivery.
5 FAQ, 14 related principles
Read the guide →
Practical guide
Tech Lead responsibilities: a practical guide
A Tech Lead is accountable for five things: the team’s technical direction, the quality of what ships, the ability to ship often without stress, reliability in production, and the team’s growth.
5 FAQ, 26 related principles
Read the guide →
The 60 principles, in one book
Every principle cited in these guides is covered in NoBullshit Tech-Lead: 240 pages for developers, Tech Leads, architects and CTOs (in French).