Learning roadmap
Leading Technical Teams
Read an engineering room without writing code: shipping rhythms, tech debt, estimation, and the questions that keep teams honest.
4 stages~6 h
That leaves 4 stages, ~6 hours of focused work. You can clear it in any order, but the stages compound — try them top-to-bottom your first time.
- You'll pick up:
delivery pipeline, code review, testing pyramid, deploy, observability
Practice quizzesLab taskBuild an "anatomy of a feature" page: a horizontal pipeline of the six stages from design to observe, each clickable to reveal what happens there, who owns it, and the classic question a leader should ask.
Build it in the LabCheckpointYou can narrate one real feature's path through your company's pipeline, including where it stalled last time.
What you'll be able to do
- Follow any engineering update — standup, incident, roadmap review — and know what question to ask next.
- Translate "tech debt" into money terms your CFO respects, and decide when to pay it down.
- Read estimation like a portfolio manager: ranges, confidence, and what "two weeks" really means.
- Run 1:1s and hiring loops that surface the truth early.
Or try a related path