Tech Leadership — Engineering Manager & Tech Lead Guide

In this tutorial, you'll learn about Tech Leadership. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Tech leadership transitions from individual contributor to team multiplier — mentoring engineers, driving architecture decisions, and shaping engineering culture at scale. Engineering managers and tech leads earn $160,000–$250,000+ and are critical to every successful engineering organization. DodaTech develops leaders who build and mentor the teams behind Doda Browser, DodaZIP, and Durga Antivirus Pro.

The Leadership Track

flowchart LR
  A[Senior Engineer] --> B{Tech Lead or EM?}
  B --> C[Tech Lead: Technical Vision]
  B --> D[Engineering Manager: People & Process]
  C --> E[Staff Engineer]
  D --> F["Senior EM / Director"]
  style B fill:#f90,color:#fff

There are two distinct leadership paths:

Many engineers start as tech leads before transitioning to management.

The IC-to-Lead Transition

What Changes

The First 90 Days

# Leadership transition checklist
def first_90_days_plan(team_size, domain_complexity):
    plan = {
        "week_1": "1:1s with every team member. Listen more than talk.",
        "week_2": "Understand current architecture, pain points, and tech debt.",
        "week_3": "Map stakeholder expectations and team morale.",
        "week_4": "Identify quick wins — small improvements with visible impact.",
        "week_5_6": "Define team vision and OKRs for the quarter.",
        "week_7_8": "Implement team rituals: standups, retros, planning.",
        "week_9_10": "Identify skill gaps and create growth plans for each member.",
        "week_11_12": "First retrospective: what's working, what's not. Adjust.",
    }
    return plan

plan = first_90_days_plan(8, "medium")
for period, action in plan.items():
    print(f"{period}: {action}")

Expected output:

week_1: 1:1s with every team member. Listen more than talk.
week_2: Understand current architecture, pain points, and tech debt.
week_3: Map stakeholder expectations and team morale.
week_4: Identify quick wins — small improvements with visible impact.
...

Leading Without Authority

As a tech lead, you'll often need to influence without direct authority:

Running Effective Technical Meetings

## Architecture Decision Record (ADR) Template

# ADR-001: Choose Database for User Service

## Status
Accepted

## Context
We need to select a database for the new user service.
Requirements: strong consistency, complex queries, ACID transactions.

## Decision
Use PostgreSQL with connection pooling via PgBouncer.

## Rationale
- ACID compliance for financial data
- Rich query capabilities for reporting
- Mature ecosystem and operational tooling
- Team has strong PostgreSQL experience

## Consequences
- (+) Strong consistency guarantees
- (+) Excellent query optimization
- (-) Manual sharding needed at scale
- (-) Higher operational overhead than managed alternatives

## Alternatives Considered
- MongoDB: lacks transaction support for financial data
- DynamoDB: limited query patterns, eventual consistency

Mentoring Engineers

The Mentoring Framework

# Track mentoring sessions
class MentorshipTracker:
    def __init__(self, mentee_name, level):
        self.name = mentee_name
        self.level = level
        self.sessions = []
        self.goals = []

    def add_session(self, date, topic, action_items):
        self.sessions.append({
            "date": date,
            "topic": topic,
            "actions": action_items,
        })

    def add_goal(self, goal, deadline):
        self.goals.append({"goal": goal, "deadline": deadline, "status": "active"})

    def progress_report(self):
        print(f"Mentee: {self.name} ({self.level})")
        print(f"Sessions: {len(self.sessions)}")
        print(f"Active goals: {sum(1 for g in self.goals if g['status'] == 'active')}")
        print(f"Completed goals: {sum(1 for g in self.goals if g['status'] == 'completed')}")

mentee = MentorshipTracker("Alex", "Mid-level")
mentee.add_goal("Lead first full project", "2026-08-01")
mentee.add_session("2026-06-15", "System design patterns",
    ["Review existing service architecture", "Read chapter on CQRS"])
mentee.progress_report()

Expected output:

Mentee: Alex (Mid-level)
Sessions: 1
Active goals: 1
Completed goals: 0

Building Engineering Culture

Key Rituals

Common Mistakes

1. Continuing to code full-time — You can't be a great manager while also being the top coder. Delegate and trust your team.
2. Avoiding difficult conversations — Unresolved conflict festers. Address performance issues and interpersonal problems directly and compassionately.
3. Making all decisions — Empower your team to make decisions. Your job is to provide context, not answers.
4. No 1:1 structure — Wandering 1:1s waste everyone's time. Have a structure: check-in, feedback, career growth, open topics.
5. Protecting the team from everything — Shield the team from noise, but don't hide all organizational context. Trust your team with reality.
6. Playing favorites — Fair treatment is non-negotiable. Recognize everyone's contributions, not just the most visible ones.
7. Not investing in your own growth — Leaders need mentors, coaches, and learning too. Join a leadership group or find a peer network.

Practice Questions

1. What's the difference between a tech lead and an engineering manager? Tech lead focuses on technical direction, architecture, and code quality. EM focuses on people, Process, and organizational health. In small companies, one person often does both.

2. How do you handle an underperforming team member? First, investigate root cause (skill gap, motivation, personal issues). Have a direct, compassionate conversation with specific examples. Create a clear improvement plan with measurable goals and regular check-ins.

3. What does a good 1:1 look like? Every other week, 30 minutes. Structure: personal check-in (5 min), project updates (10 min), career growth/feedback (10 min), open topics (5 min). The agenda should be driven by the team member, not the manager.

4. How do you build trust with a new team? Listen first, act second. Don't make changes in the first 30 days without understanding context. Be transparent about your decision-making. Follow through on commitments.

5. Challenge: Pick a struggling project or team Process in your organization. Design a turnaround plan using the principles in this guide. Include stakeholder analysis, communication Strategy, improvement milestones, and success metrics. Present it to a peer for feedback.

Real-World Task

Shadow a tech lead or engineering manager in your organization for one week. Observe how they handle 1:1s, planning meetings, technical decisions, and stakeholder communication. Write a Reflection on what you'd do differently and what you'd adopt.

FAQ