ELBTG
Get the Book

Your journey

Where are you on the path?

Pick the altitude that matches your Tuesday, not your LinkedIn headline. Each stage names the work, the stall, and the next move.

  1. The work

    Engineer

    You are learning to be trusted with real systems. Craft is the whole game — and that is correct, for now.

    Now

    • Ship complete, well-tested work
    • Ask better questions in design reviews
    • Learn the product, not just the ticket

    How people get stuck

    • Waiting to be invited before having an opinion
    • Optimizing locally without knowing the customer

    Next

    • Write a design doc someone else can implement
    • Mentor an intern or a new hire
    • Present a decision, not a status
    ChapterChapter

  2. The problem

    Senior Engineer

    You are the person who can be given a fuzzy problem. The trap is becoming the team's finishing machine.

    Now

    • Scope work for others, not just yourself
    • Make quality the default, not a personal hero story
    • Start building influence in rooms you do not run

    How people get stuck

    • Being the bottleneck 'because it's faster if I do it'
    • Confusing seniority with being the best coder in every thread

    Next

    • Lead a cross-team design
    • Give feedback that changes how someone works
    • Learn how your work shows up in the business
    ChapterChapter

  3. The team’s technical bet

    Tech Lead

    You are accountable for the technical outcome of a group. Authority is thin. Influence is the job.

    Now

    • Facilitate, don't dominate, design
    • Sequence work against a bet, not a pile
    • Represent the team upward without becoming a translator of complaints

    How people get stuck

    • Still writing the critical path after midnight
    • Avoiding conflict between strong engineers

    Next

    • Install a decision ritual the team can run without you
    • Coach a senior toward the lead role
    • Brief an executive without a slide novel
    ChapterChapterChapter

  4. The people and the output

    Engineering Manager

    The identity shift. Your output is now other people's output. Most careers either transform here or quietly fail.

    Now

    • 1:1s about the person, not only the project
    • Hiring, performance, and air cover
    • Protecting focus while remaining a partner to product

    How people get stuck

    • Player-coach who never leaves the field
    • Becoming a status router between Slack and slides

    Next

    • A bench of two people who could stretch into your seat
    • A written team strategy, not a copied roadmap
    • A relationship with a peer in another function that can survive bad news
    ChapterChapterChapter

  5. The system of teams

    Director

    You no longer lead a team. You lead leaders. The work is coherence, capacity, and culture across groups.

    Now

    • Portfolio thinking: a few bets, not many projects
    • Developing managers as a first-class job
    • Interfaces between teams as a design problem

    How people get stuck

    • Skipping a level and managing your managers' teams
    • Heroic firefighting as a substitute for structure

    Next

    • A succession plan you could live with
    • A voice in company-level tradeoffs
    • Metrics that measure the system, not your activity
    ChapterChapterChapter

  6. The function

    VP of Engineering

    You own a function in a company, not a craft in a corner. Politics, capital, and narrative become first-class tools.

    Now

    • Partnering with product, finance, and GTM as a peer
    • Building an org that can hire, keep, and grow leaders
    • Telling a true story about technical risk to a board

    How people get stuck

    • Still the architect of last resort
    • An org chart that only you understand

    Next

    • A leadership team that disagrees with you in the room
    • A multi-year technical bet with a commercial hook
    • Time spent on culture as if it were production
    ChapterChapterChapter

  7. The company

    CTO / Technology Executive

    Technology is now a way the company competes. You hold craft, capital, and credibility in the same hand.

    Now

    • A technology strategy that is also a business strategy
    • A bench that could survive your departure
    • Judgment about what not to build, including the fashionable things

    How people get stuck

    • Nostalgia for the architecture you personally understand
    • Innovation theater detached from customers

    Next

    • Develop two people who can argue you out of a bad bet
    • Install a leadership academy so the pipeline does not depend on charisma
    • Keep a beginner's posture toward the market
    ChapterChapterChapter