Career path
Lead teams
Move work through people, not only through code.
Code review, mentoring, planning, stakeholder communication, estimations and conflict resolution.
Senior engineers, new tech leads and mobile leads who need practical leadership habits.
Are you on this path?
Signs you are here
- You are the strongest individual contributor, but work still bottlenecks on you.
- Your code reviews block more than they grow people.
- Planning and stakeholder updates feel like overhead you avoid.
- You were made a lead and nobody explained the actual job.
Work this path deliberately.
Use the books, resources and writing in this path to solve one career problem at a time.
- 1
Read the symptoms and confirm this is your current bottleneck.
- 2
Take the first move below to make the problem concrete.
- 3
Pick the book when you need the full system.
- 4
Return to the paths when the next career pressure changes.
Books for this path
Senior engineers, new tech leads and mobile leads who need practical leadership habits. Code review, mentoring, planning, stakeholder communication, estimations and conflict resolution. Every book here is written from the hiring side, from 500+ technical interviews, and each book page shows what is inside and who it is for.
Free resources
Free checklists, cards and templates for the lead teams path. Each one is short enough to use on the problem you have this week, and each works on its own, before or without a book.
Writing for this path
Technical leadership
Best books for tech leads and staff engineers
Most lists of the best books for tech leads and staff engineers rank the same titles and stop. This one groups eleven books by the problem you have this quarter: the role is unclear, you are choosing a track, you are right and nothing moves, teams keep colliding, or the hard part is the system itself. For each, who it is for and what it leaves out. Three are mine, and I say so where they appear.
13 min read
Technical leadership
Tech debt business case: a one-page template, and how to get it funded
"We need a sprint for tech debt" is usually right about the code and usually unfunded. A debt case gets funded when it names the decision and the one person who owns the capacity, prices the debt as interest and principal in units your tools already record, and speaks in what that person is scored on. A one-page template you can copy, a filled example, and what to do with a partial yes or a no.
18 min read
Technical leadership
A project status update template for tech leads that cannot hide red
Most status updates report effort and a colour, and the colour is a mood. A status update template for tech leads where green has to be earned: status definitions tied to evidence, an end-to-end path test behind every green, four lines that carry the week, and how to report bad news while it is still a planning input.
14 min read
Technical leadership
A technical design doc template for staff engineers, and when an ADR is enough
Most design docs describe a solution well and still fail, because nobody named who decides, the objection arrived in the meeting, and nothing said what would reopen the call. A complete design doc template you can copy, what each section is for, how a staff engineer gets it approved, and when a short ADR does the job instead.
16 min read
Technical leadership
Engineering manager vs tech lead: who owns what, and what each is judged on
The tech lead owns decisions about the system. The engineering manager owns decisions about people and capacity. Most comparisons stop there. This one, from the hiring side, adds what each role is evaluated on, the exact place a tech lead's authority stops, how to choose between the two paths, and what interviewers ask each.
15 min read
Technical leadership
From senior developer to tech lead: what changes when the outcome is yours and the authority is not
The transition from senior developer to tech lead is not more of the same work. Your name goes on an outcome that depends on teams you do not manage, and being right stops being enough. What changes, a first 90 days built from that, the tech lead responsibilities that are evaluated, and the mistakes that keep strong engineers stuck.
16 min read
Technical leadership
Disagree and commit: what engineers owe after the call
Disagree and commit is usually taught as a meeting habit. For engineers, the commit half happens later, in pull requests, review comments and status reports. When to disagree, how to record the disagreement, what commit obliges you to do, the reopen criteria that keep the door open, and the risks you should never commit to.
19 min read
Technical leadership
How to say no to a project as a tech lead, with the exact words
"There is no way we hit that date" is usually true, and it usually fails. A tech lead rarely owns the decision to drop a project or move a date. What you own is making the trade visible: whose call it is, the promise hiding inside the date, three options with one recommended, and the words that hand the choice back.
13 min read
Technical leadership
How to escalate as a tech lead without starting a status war
Most escalations that go wrong were right to happen and wrong in the way they were fired: too late, too loud, to an audience instead of an owner. How to escalate as a tech lead: find the decision first, name the threshold before you need it, and send a brief the owner can decide without reconstructing the conflict.
17 min read
Technical leadership
Green on the dashboard, red in reality: what a tech lead does, and what the interviewer listens for
Every team is green, and the feature has never once worked end to end. False green is rarely a lie. It is the truth from the wrong instrument. What a tech lead changes, the sentence that goes to the sponsor, and what an interviewer listens for when they ask how you know a project is on track.
12 min read
Career strategy
The engineer nobody chases
The most common reason capable engineers stall has nothing to do with code. It is how much coordination work lands on other people after you have finished.
7 min read
Architecture
How to review a mobile architecture proposal
A practical review framework for mobile architecture decisions: constraints, reversibility, ownership, migration and production proof.
4 min read
Technical leadership
Tech lead code review is a system
Good code review is a system for quality, ownership, mentoring and risk control.
3 min read
