Team Lead Roadmap

Tap menu for chapters & tools

Career path

Team Lead Roadmap

A phased path from trusted senior engineer to effective team lead - and the altitude after that. Select a phase to see outcomes, skills, and concrete practices.

Created by Amin Sharifi

Pillar 01

People who compound

Coach, challenge, and grow humans so the team gets stronger without you in every ticket.

Pillar 02

Execution that ships

Priorities, ownership maps, quality bars, and delivery systems that finish what matters.

Pillar 03

Architecture that endures

Boundaries, system design, evolution, and operability under real production pressure.

Pillar 04

Communication that scales

Writing, facilitation, stakeholder updates, and listening that keep truth moving fast.

Pillar 05

Judgment under fog

Trade-offs, risk, ethics, and the courage to push, pause, or reverse a decision.

Pillar 06

Self as the platform

Energy, boundaries, learning loops, and calm leadership when the room gets loud.

Phase 0 · Ongoing while senior

IC Foundation

Become the engineer others trust with hard problems and hard truths.

Outcomes

  • Reliable delivery with clean communication
  • Strong code review and design judgment
  • Mentors juniors without being asked

Skills to build

Technical depthWritten RFCsSystem design basicsMentorshipIncident response

Practices

  • Lead a project end-to-end including stakeholder updates
  • Write one ADR for a non-trivial design choice
  • Write postmortems that teach the org
  • Run a design workshop or architecture brown-bag
  • Ask for feedback on collaboration, not only code quality

How to use this roadmap

Pick your phase honestly

Title lag is common. Choose the phase that matches behaviors, not the org chart.

One practice per week

Depth beats checkbox tourism. Master a few habits before expanding the list.

Review quarterly

Ask peers and your manager for evidence against outcomes - not self-grades alone.

Further reading

Suggested books for this path

Books that deepen the soft skills, architecture, and system design threads in this guide. Start with Fournier, then branch by stage.

  1. Start here (tech lead to EM)

    The Manager's Path

    Camille Fournier

    The most cited map of engineering leadership levels, from mentoring and tech lead through management. Matches the mindset and operating chapters in this guide.

    Pairs withMindset, Operating the Team, 90 Days

  2. First months as a people manager

    The Making of a Manager

    Julie Zhuo

    Warm, concrete first-time manager playbook for feedback, hiring, and purpose. Excellent if you just got reports and feel under-trained.

    Pairs withFeedback, Self-Management

  3. Coaching and change

    Resilient Management

    Lara Hogan

    Practical tools for 1:1s, feedback, and leading through change without burning out. Short enough to re-read when a people situation heats up.

    Pairs withFeedback, Trust, Self-Management

  4. Hard conversations

    Radical Candor

    Kim Scott

    A clear model for care + challenge in feedback. Helps you leave both the brutal honesty and ruinous empathy traps common for new leads.

    Pairs withFeedback, Conflict & Trust

  5. Lead without the management ladder

    Staff Engineer

    Will Larson

    Shows how senior ICs create impact through sponsorship, technical strategy, and org work. Perfect if you lead without direct reports.

    Pairs withInfluence, Decisions

  6. Org and team design

    Team Topologies

    Matthew Skelton & Manuel Pais

    Team types and interaction modes for cognitive load and fast flow. Pair with the Team Topology Patterns chapter.

    Pairs withTeam Topologies, Operating, System Architecture

  7. Delivery systems

    Accelerate

    Nicole Forsgren, Jez Humble, Gene Kim

    Evidence-backed view of what drives software delivery performance. Use with DORA and operating rhythm chapters.

    Pairs withOperating, Stakeholders

  8. System design depth

    Designing Data-Intensive Applications

    Martin Kleppmann

    The reference for storage, replication, partitioning, and streams when design debates get hand-wavy.

    Pairs withSystem Design, System Architecture

  9. Architect-as-lead

    Fundamentals of Software Architecture

    Mark Richards & Neal Ford

    Styles, quality attributes, and the soft skills of architecture decisions.

    Pairs withArchitecture Practices

  10. Distributed trade-offs

    Software Architecture: The Hard Parts

    Neal Ford, Mark Richards, et al.

    Service granularity, data ownership, and the painful parts of distributed systems.

    Pairs withSystem Architecture

  11. Interview + practice

    System Design Interview (Vol 1 & 2)

    Alex Xu

    Step-by-step large-scale designs. Pair with free ByteByteGo videos and chapter drills.

    Pairs withSystem Design, Interview prep

  12. Design principles

    Clean Architecture

    Robert C. Martin

    SOLID and component boundaries that keep business logic free of framework gravity.

    Pairs withArchitecture Practices

  13. Flow and constraints

    The Phoenix Project

    Gene Kim et al.

    Narrative intro to bottlenecks, WIP, and IT flow. Good intuition pump before heavier ops books.

    Pairs withOperating, Decisions

  14. Trust and conflict

    The Five Dysfunctions of a Team

    Patrick Lencioni

    Simple model for trust, conflict, commitment, accountability, and results.

    Pairs withTrust, Feedback

  15. Product partnership

    Inspired

    Marty Cagan

    How strong product orgs work with engineering. Helps leads partner instead of order-take.

    Pairs withStakeholders, Decisions

  16. Systems of teams

    An Elegant Puzzle

    Will Larson

    Staffing, team size, migrations, and manager judgment for multi-team problems.

    Pairs withTeam Topologies, Hiring, Operating

  17. Classic systems thinking

    High Output Management

    Andrew S. Grove

    Leverage, meetings as media, task-relevant maturity. Dense classic. Read slowly after Fournier.

    Pairs withOperating, Self-Management