How does a tech lead differ from a senior individual contributor (IC)?

Question

Accepted Answer

A **senior IC** is judged mainly by what *they* build: hard problems solved, high-quality code, deep expertise. A **tech lead** is judged by what the *team* builds. The title is less a promotion above senior IC and more a different shape of work focused on multiplying others.

## The key shift

```text
Senior IC                         Tech Lead
----------------------            ----------------------
Depth in the code                 Breadth across the project
Solves the hard problem           Makes sure the right problems get solved
Optimizes own throughput          Optimizes the team's throughput
Owns a component                  Owns the technical outcome
Mostly heads-down                 Mix of heads-down and coordination
```

## A concrete example

Faced with a tricky bug, a senior IC's instinct is to dig in and fix it. A TL's instinct is to ask: is this the best use of *my* time, or should I coach a teammate through it so they learn and I stay free to unblock others? Both answers can be right; the TL has to consciously choose.

## The trade-off

You give up some of the deep, satisfying focus time of pure IC work. In return you get leverage. Many strong ICs try TL, find they miss the code, and go back, and that is a perfectly healthy choice, not a failure.

## Why it matters

Conflating the two roles leads to a common failure: a TL who acts like a senior IC, hoarding the interesting work and leaving the team unled.

Knowing the difference helps you decide whether you actually want the role, and helps you do it well if you take it.