Team Lead: The Role, vs Tech Lead, vs Engineering Manager

· by Marian Kamenistak

A team lead is an engineer who leads one team, usually while still writing code. It is 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.

That ambiguity is not a detail. It is the main thing to understand about the title.

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 close to the modal opening sentence of a first session.

The three jobs hiding under one title

  1. Coordinator lead. Runs planning, standup, and the Jira board. People and technical authority stay elsewhere. Common in enterprises and agencies.
  2. Tech-lead flavored. Owns architecture and technical decisions for the team. People stuff belongs to an engineering manager one level up.
  3. 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 cannot carry. First, “tech lead” and “team lead” swap meanings between companies, and arguing about the labels is pointless: ask what the role owns. Second, the staff engineer column is a different track entirely, multiplication through influence instead of authority. I wrote about it separately in What a Staff Engineer role is all about.

The transition that actually 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 are still deciding whether to take the step at all, start with should I become a team lead and its 3-minute readiness test.

Marian Kamenistak in a 1:1 mentoring session.
This is where most new leads first say the transition out loud.

The three failure patterns I see most in first sessions:

  1. The hero. Keeps taking the hardest tickets, reviews everything, becomes the bottleneck. Team learns to wait.
  2. The shield that overheats. Absorbs all pressure from above, tells the team nothing, burns out quietly.
  3. The peer who can’t switch. Was friends with everyone last month, now avoids every hard conversation, and the strongest engineer on the team is already interviewing elsewhere.

All three are survivable, and none of them fix themselves. If you are 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.

Frequently asked

What is a team lead in software engineering?+
A team lead is an engineer who leads one team while usually still writing code. Depending on the company, the role covers technical direction, people responsibility, or both. It is the most common first step from engineer into leadership.
What is the difference between a team lead and a tech lead?+
A tech lead owns the technical direction of a team: architecture, code quality, technical decisions. A team lead often adds the people side: 1:1s, feedback, sometimes performance and hiring. In many companies the titles are used interchangeably, so ask what the role actually owns before accepting it.
What is the difference between a team lead and an engineering manager?+
An engineering manager owns the people side fully: performance, careers, hiring, firing, and delivery accountability, with little or no coding time. A team lead usually keeps a majority of their time in code and carries a lighter version of the people load. The EM role is where the IC-to-manager switch becomes permanent.
Do team leads still write code?+
Usually yes, around half their time or more. The trap is that the calendar fills with meetings while the team still expects code output. The honest version of the role names a percentage, protects it, and drops it deliberately as the people load grows.
How do I move from software engineer to team lead?+
Start doing parts of the job before the title: run the planning, own an initiative across people, mentor a junior. Then make the ask explicit. 52% of the leaders I mentor started exactly here, in their first lead role, usually promoted for engineering skill and left alone with the people part.

Read next

New posts, straight to your inbox.