Make the IC-to-decider transition that defines the tech lead role. Build the mentoring, debate-stewarding, uncertainty-communicating, and direction-setting skills that distinguish a lead from a senior IC with the title. The framework-author model of technical leadership is instructive precisely because it runs on no positional authority: direction gets set in writing, in named, defensible positions compressed into phrases that travel ("convention over configuration," "the majestic monolith") — engineers downstream don't carry your full reasoning into their decisions; they carry your phrase, so make the phrase right. Direction gets demonstrated rather than described — the proof-of-concept that shows the approach beats the treatise that argues it. And the complementary register matters as much: for every polemicist-architect voice there is a teacher-at-large voice — gentler, pedagogical, focused on growing engineers rather than directing architecture — and most leads over-develop one and starve the other. "I intend to," meanwhile, is an architectural move you already know: converting the team from RPC (ask the coordinator) to event-driven (declare intent on the bus) — decision latency moves to the edge, the coordinator stops being the bottleneck, and the system scales.
This course unlocks once you've finished its prerequisite. Open prerequisite →
Tech Lead is a role change, not a promotion, and most engineers who fail at it fail because nobody told them that. The unit of your output changes: from your code to the team's cl…
Tech lead is not a promotion; it's a role change, and most engineers treat it as the former and fail at the latter. As an IC, your output is the code you ship, your judgment serve…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Approach: Reference
Approach: Reference
1. The retrospective. If you've held a lead role (formally or de facto), write one page: what you got right (no false modesty), what you got wrong, what you'd do differently, whic…
11 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.