Tech Lead vs Engineering Manager. Which Path Is Right for You?
Most engineers assume it's a one way ladder. It isn't.
You’re good at your job. People have noticed. And at some point, maybe in a performance review or over a coffee with your manager, someone asks: “Have you thought about where you want to go next?”
Suddenly you’re looking at what feels like a fork in the road. Tech Lead or Engineering Manager. Both sound like progression. Both come with more responsibility. But they are not the same thing, and choosing the wrong one, or choosing for the wrong reasons, is one of the most common career mistakes I see engineers make.
Before we get into the differences though, there’s something worth saying upfront.
This week’s newsletter is brought to you by EM Accelerator.
If you’re navigating the move into engineering leadership, EM Accelerator is the practical training built specifically for engineering managers who want to stop figuring it out alone. 7 modules, real frameworks, community access, and direct access to me. Join 110+ engineering leaders already on the completely free waitlist at emaccelerator.com.
It’s Not a One Way Ladder
A lot of engineers assume the progression goes: engineer, tech lead, engineering manager, and so on up the chain. That EM is simply the next rung after tech lead. It isn’t.
These are two separate career paths, not steps on the same one. And there are others too. The staff engineer and principal engineer route is a legitimate, well compensated, highly respected path that keeps you deeply technical without asking you to manage people. Some of the most impactful people in engineering never manage anyone.
The other thing worth knowing is that you are not stuck once you choose. Plenty of great EMs spent time as tech leads first. Plenty of great tech leads tried EM, realised it wasn’t for them, and came back to the technical path better for the experience. It is not a one way door. But the earlier you get honest with yourself about what you actually want, the less time you waste going in the wrong direction.
What Both Paths Have in Common
Here’s what most people miss when they’re weighing this up. Both the tech lead and engineering manager paths ask for the same fundamental shift.
Whether you go one way or the other, you have to genuinely make peace with becoming less and less hands on over time. Not grudging acceptance. Actual peace.
As a tech lead you write less code and review more. You spend more time in conversations, documents, and decisions. As an EM you may stop writing code altogether. The craft that made you successful as an engineer, probably the thing you love most about the job, becomes something you do less of, then rarely, then perhaps not at all.
This is what trips people up. They spend weeks debating tech lead versus EM without sitting with the more important question underneath: am I actually ready to let go of being an individual contributor?
The people who thrive in either role are the ones who find real satisfaction in what replaces the hands on work. Influence, mentorship, technical strategy, watching people grow because of something you did. If that doesn’t appeal to you yet, neither path is the right move. Knowing that is its own kind of clarity.
Free Scored Role Reality Checker for Paid Subscribers
I’ve created a Role Reality Checker Worksheet for paid subscribers.
It’s a simple, practical tool with:
✅ 14 statements across 4 categories to help you understand how you’re actually wired
✅ Three columns to tick - Tech Lead, Engineering Manager, or Neither
✅ A scoring guide to interpret where your answers cluster
✅ A reflection prompt to help you sit with the bigger question underneath the choice
If you’re genuinely weighing up which path is right for you, this is worth 10 minutes of honest self-reflection. Most people never do it, and then wonder why they ended up in the wrong role.
👉 Subscribe and get the worksheet
Nobody Trains You for Either Role
Here’s something else nobody talks about enough. Both the tech lead and engineering manager roles come with almost no formal training. You are largely expected to figure it out as you go.
You get the title. You get the new responsibilities. And then you get thrown in. Most people learn through trial and error, picking up what they can from managers they’ve had, articles they’ve read, and mistakes they’d rather forget.
This is one of the reasons the transition is so hard. You spent years getting good at engineering. There were clear problems, clear feedback loops, clear ways to measure progress. Leadership doesn’t work like that. The feedback is slower, the problems are messier, and there’s rarely a right answer.
Knowing this going in doesn’t make it easy. But it does mean you can be more intentional about seeking out learning rather than assuming it will just happen.
The Tech Lead Reality
The tech lead role is one of the most misunderstood in engineering.
You carry high expectations. Architecture decisions, technical direction, code quality, raising the bar across the team. That sounds straightforward. The catch is you carry all of that with almost no formal authority. Nobody reports to you. You cannot tell people what to do. You have to lead through influence, through the quality of your thinking, the strength of your relationships, and your ability to bring people with you rather than directing them.
That gap between high expectations and low formal authority is where most new tech leads struggle. You need to convince rather than instruct. You need to earn trust rather than assume it. And you need to be comfortable with the reality that the team might not always follow your recommendation, and you have to find a way to move forward anyway.
If that kind of challenge energises you, the tech lead path has a lot to offer. If that ambiguity frustrates you, it will wear you down.
The Engineering Manager Reality
The EM role asks something different. Your job is no longer to be the best engineer in the room. Your job is to make everyone else in the room better.
Your success is measured through other people. Their growth, their performance, their output, their wellbeing. That is a completely different success metric to the one that got you here. As an engineer you could point to things you built. As an EM the things you build are invisible. A team that trusts each other. A culture where people do their best work. An engineer who got promoted because of conversations you had with them months ago.
You will also have hard conversations on a regular basis. Performance issues. Conflict between team members. Difficult feedback. Redundancies. These don’t get easier just because you get more experienced. You get better at handling them, but they stay hard.
The Tech Lead and EM Relationship
One thing that often gets overlooked in this conversation is how important the relationship between tech lead and EM actually is.
When it works well it’s one of the most powerful partnerships in a team. The EM handles the people side, the processes, the organisational noise. The tech lead drives technical direction. Together they give the team both strong leadership and strong technical guidance.
But it only works when there’s genuine trust and honesty between them. They need to be aligned. They need to be able to challenge each other behind closed doors and present a consistent front to the team. When that relationship breaks down, or when they’re not honest with each other about what’s working and what isn’t, the team feels it even if nobody says anything out loud.
If you’re choosing the tech lead path, the quality of your relationship with your EM will shape your experience of the role more than almost anything else.
Four Questions Worth Sitting With
Rather than a checklist, try sitting with these honestly:
Do you get energy from problems or from people? Not which sounds better. Which one actually fills your tank at the end of a hard week.
How honest are you being about giving up the hands on work? Sit with the idea of not shipping code for a month. Does that feel like relief or dread?
Do you want to own outcomes or influence them? EMs own outcomes but often can’t control exactly how the work gets done. Tech leads influence technical decisions but rarely have the final word. Which feels more natural to you?
How do you feel about hard conversations? Not technical disagreements. The human ones. If you avoid those conversations now, the EM role will put them in your calendar regardless.
The Career Paths
Tech lead opens toward staff engineer, principal, distinguished engineer. Deeply technical, increasingly strategic, and some of the most valued roles in the industry.
EM opens toward senior EM, director, VP of engineering, CTO. Broader people and organisational responsibility, eventually owning the entire engineering function.
Neither is better. But knowing which direction you want to head tells you which path to start building on now. And remembering that you can change course, especially early, takes some of the pressure off making the perfect call today.
Final Thoughts
There is no universally right answer. There is only the right answer for you, right now, based on what you actually want. Not what sounds impressive, not what your manager is nudging you toward, not what your peers are doing.
Both paths will ask you to grow in uncomfortable ways. Both will ask you to let go of things you’re good at. Both will give you something new and genuinely meaningful in return, if you pick the one that fits how you’re actually wired.
If you’re leaning toward the EM path and want to understand what the role actually looks like day to day, I’m building something specifically for that. Join 110+ engineering leaders already on the waitlist at emaccelerator.com.
Liked this, even a tiny bit or feel sorry for me? Make sure to click the like button ❤.
Think someone else might find this useful or you just want to make fun of me together? Make sure to share this post 🔗.
Want to write a guest post for this newsletter? Let me know!
The FREE waitlist for my new premium training for Engineering Managers is now live.
I’ve launched a new YouTube channel.
Check me out on LinkedIn. I’m at >58,000 followers now.