The Tech Lead vs Engineering Manager Decision

What you actually need to know

• Tech lead and engineering manager are different careers, not adjacent steps.
• The skills overlap less than the title implies.
• Both ladders should pay comparably. Compensation is rarely the right signal.
• Pick by what energizes you, not by what is available in your current company.
• The switch is possible later but has a cost. The first choice matters.

The core argument

The most common career mistake I see in software is engineers becoming managers because that is the only promotion their company offered, not because they wanted to manage. The cost shows up in two ways. The engineer is unhappy in the new role because the rewards are different and slower. The team is poorly served because the new manager is doing the job for the title, not for the work.

Tech lead and engineering manager look like adjacent steps. They are different jobs that happen to share an organization chart. A tech lead's day is code, design, and technical review. An engineering manager's day is people, planning, and coordination. Both are valuable. Both are hard. They reward different temperaments.

The choice should follow temperament. Ask what energizes you. If solving a hard technical problem on a Friday feels like progress, you are an IC. If helping an engineer through a stuck point feels like progress, you are an EM. Both answers are correct. Both are needed. Picking the one that does not match your temperament is how strong engineers become mediocre managers and how strong managers lose touch with the work.

The other half of the choice is structural. If your company does not have a real IC ladder, the choice gets distorted because the only path to senior compensation is through management. That is a company problem, not a fit problem. Either advocate for a real IC ladder or move to a company that has one. Becoming an EM you do not want to be because the comp is right is a multi-year cost.

What each job actually looks like

Tech lead

You are still an engineer. You write code, design systems, and own the technical direction of a project or team. You also spend more time on review, architecture conversations, and unblocking other engineers. You have leverage through technical influence, not through formal authority.

The rewards are immediate. You shipped a thing. You designed the thing that shipped. Your name is on the architectural decisions that made the work go well. The satisfaction loop is short.

The challenges are political and organizational. You have to influence without authority. You have to articulate technical decisions to people who do not write code. You have to balance the team's autonomy with the need for technical coherence.

Engineering manager

You optimize the team's outcomes through other people. You hire. You run 1:1s. You make performance decisions. You shape what the team works on. You coordinate with other teams. You communicate up to leadership. You write less code, sometimes none.

The rewards are slower and more diffuse. An engineer you hired six months ago is now shipping well. A process change you made a year ago is paying back now. The team you built handled an incident gracefully. None of this is as visceral as shipping a feature.

The challenges are different. You absorb the team's stress and protect them from political noise. You make decisions that affect careers, including ones that will be unpopular. You measure your week by other people's progress, which is a different psychology than measuring your week by your own.

How long does it take to know what you want

What a good choice looks like

• You picked it because the work energizes you, not because it was the next title.
• Your company has a real ladder for the path you chose.
• You have a mentor who has walked the path you are starting.
• You have a six-month review built in to confirm the fit.
• You have a known path back if it turns out wrong.

Expert opinion

I have seen brilliant engineers become unhappy managers and decent engineers become exceptional managers. The variable is not skill. It is fit. The people who thrive as EMs love the indirect satisfaction of helping a team ship. The people who thrive as senior ICs love the direct satisfaction of building. Both contributions are essential. The mistake is treating EM as the only valid promotion and then being surprised when half the EMs would rather be coding.

>

Yashveer Singh, founder of Yashveer Labs

How this played out on a real project

A senior engineer I worked with took an EM role because it came with a 30 percent raise and the only available promotion. Six months later he was miserable. The work he loved (debugging, designing systems, mentoring through code) was gone. The work he had taken on (performance reviews, headcount planning, status updates to leadership) drained him.

We talked through it. He moved back to a staff engineer role at a different company that had a real IC ladder. Compensation was comparable. Energy returned within weeks. The lesson was not that EM was wrong; the lesson was that EM was wrong for him, and he had taken it for the wrong reasons. The pattern matches going from engineer to founder and the engineering career plateau and how to break it.

Common mistakes

1. Taking the EM role because it is the only promotion available, not because the work fits.
2. Staying as a tech lead at a company without a real IC ladder for five years.
3. Treating either path as a one-way door.
4. Picking based on compensation rather than fit.
5. Trying to be both EM and full IC and burning out.
6. Not having a known way back if the new role does not fit.
7. Ignoring the temperamental difference between immediate and delayed rewards.

A 90 day plan to make the choice

1. Weeks one and two. Identify what energizes you in your current work. Track it honestly for two weeks.
2. Weeks three and four. Talk to a tech lead and an EM you respect. Ask them what their week looks like and what they like and dislike about it.
3. Weeks five to eight. Audit your company's ladder. Is there a real path for both? If not, factor that in.
4. Weeks nine to twelve. Decide. Communicate the decision. Build in a check-in at six months to confirm the fit.
5. Ongoing. Treat the choice as reversible. Both paths are valid. The mistake is choosing once and never reassessing. The discipline lines up with the engineer's five year plan and why some engineers stay junior for a decade.