A team lead is an engineer who leads one team, usually while still writing code. It’s the most common first leadership role in software, and the most under-defined: in one company it means “senior engineer who runs standup”, in the next it carries real people responsibility.
In practice, that ambiguity is the first thing to sort out about the title, before compensation, before anything else, because most of the pain I see in first sessions traces back to skipping it.
My base for this guide: 3,400+ mentoring sessions with 300+ engineering leaders since 2019. 52% of my mentees are in their first leadership role, and “I became a team lead and nobody told me what the job is” is the sentence I hear most often when a first session opens.
The three jobs hiding under one title
- Coordinator lead. Runs planning, standup, and the Jira board. People and technical authority stay elsewhere. Common in enterprises and agencies.
- Tech-lead flavored. Owns architecture and technical decisions for the team, while the people side belongs to an engineering manager one level up.
- Proto-EM. Runs 1:1s, gives feedback, feeds into performance and hiring, codes half-time. This version is an engineering manager role on training wheels, whether the company admits it or not.
Before taking any team lead role, get the answer in writing to one question: which of these three is it? Misreading this is how engineers end up accountable for people outcomes with no mandate, or blamed for architecture they never owned.
Team lead vs tech lead vs engineering manager vs staff engineer
| Team Lead | Tech Lead | Engineering Manager | Staff Engineer | |
|---|---|---|---|---|
| Primary ownership | One team’s day-to-day | One team’s technical direction | People, performance, delivery | Cross-team technical impact |
| Code time | ~50%+ | ~50-70% | ~0-20% | Varies, prototypes over features |
| Does 1:1s | Sometimes | Rarely | Always | No, mentors instead |
| Performance and hiring | Light or none | No | Yes, fully | No |
| Next step usually | EM or tech lead | Staff engineer or EM | Senior EM, director | Principal engineer |
Two clarifications the table can’t carry. First, “tech lead” and “team lead” swap meanings between companies, and arguing about the labels is pointless, ask what the role owns instead. Second, the staff engineer column is a different track entirely, multiplication through influence, as opposed to authority. I wrote about it separately in What a Staff Engineer role is all about.
The transition that hurts
The move from engineer to lead is the only career step where the thing that got you promoted, your individual output, becomes the thing you must give away. Nobody warns you that the first month feels like getting worse at your job. If you’re still deciding whether to take the step at all, start with should I become a team lead and its 3-minute readiness test.
The three failure patterns I see most in first sessions:
- The hero. Keeps taking the hardest tickets and reviewing everything, and within a quarter the team has learned to wait.
- The shield that overheats. This one absorbs every bit of pressure from above, tells the team nothing about it, and burns out quietly.
- The peer who can’t switch. Last month they were friends with everyone. Now every hard conversation gets avoided, and the strongest engineer on the team is already interviewing elsewhere.
All three are survivable, and none of them fix themselves. If you’re in the middle of this move, this is precisely what 1:1 mentoring for engineering managers and leads exists for. The intro session is free, and yes, “I have been a lead for two months, is it too early” is a fine reason to book it.