Level Up: Choosing The Technical Leadership Path
summary
A clear claim: technical leadership = aligning a group in a technical context, not vague management. Evidence: a rescue social‑app effort (8–10 acquired companies, ~600 people across five countries) fails from misalignment. Practical diagnostics: inspect git pull‑request reviews and duplicated implementations (eight different email senders). A concrete path appears as a five-step recipe: find misalignment, own the issue, get sponsorship, finish the work, celebrate and repeat. Career framing uses a trident model (technical leadership, individual contribution, management).
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:23Agenda
- 1:44Exploring technical leadership
- 25:15Reasons for you
- 32:12How to get started
- 40:11Outro
related talks
44mTalking with Tech Leads
24mTechnical Excellence in Technical Leadership
58mMy Journey to Understanding Technical Leadership
35mTalking With Tech Leads
47mLeading in Tech
12mLeader or engineer? Navigating our technical identity crisis
31mFlavours of technical leadership
16mThe secret to technical leadership
