What is a tech lead and what are the core responsibilities?

Question

Accepted Answer

A **tech lead (TL)** is the engineer accountable for the technical success of a team or project. You still write code, but your primary job shifts from *just building* to *making sure the right things get built well*. A TL is a force multiplier: your impact is measured by what the team ships, not just by your own commits.

## Core responsibilities

```text
✓ TECHNICAL DIRECTION → set architecture, standards, and the "how" of the project
✓ DELIVERY → break work down, unblock people, keep the project on track
✓ QUALITY → code review, testing culture, keeping the codebase healthy
✓ MENTORING → grow the engineers around you
✓ COMMUNICATION → translate between engineering and stakeholders
✓ DECISIONS → make (or facilitate) technical decisions and own the outcome
```

## A concrete example

Your team is asked to add payments. As TL you don't just pick up tickets. You sketch the approach (use a payment provider vs. build), split it into shippable slices, decide who works on what, review the risky parts of the code yourself, and tell the product manager what is realistic by when.

## A common misconception

New TLs often think the title means "the best coder." It doesn't. It means the person responsible for the team's technical outcomes. Sometimes the most valuable thing you do all day is a 15-minute conversation that unblocks three people.

## Why it matters

A team without a clear technical owner drifts: decisions stall, quality slips, and engineers pull in different directions.

Understanding that the role is about leverage, not heroics, is the first step to doing it well.