Guides

Tech Lead vs. Engineering Manager: Clarifying the Roles

By Marc Molas·August 14, 2023·10 min read

"So, are you the tech lead or the manager?" It's a question that shouldn't be confusing, but in most engineering organizations under 50 people, it is. Because they've put one person in both roles and called it leadership.

I've seen this pattern repeat across dozens of startups: a strong senior engineer gets promoted to "lead." Suddenly they're responsible for architecture decisions, code quality, mentoring junior developers, running sprint ceremonies, doing performance reviews, shielding the team from stakeholder chaos, hiring, and -- oh right -- still writing code. They're set up to fail, and they usually do, burning out in one dimension while dropping balls in the other.

The Tech Lead and the Engineering Manager are fundamentally different roles. Conflating them doesn't save headcount -- it degrades both functions. Let's clarify what each does, when to split them, and how to build career paths for both.

The Tech Lead role

The Tech Lead owns the technical direction of a team or project. Their domain is the code, the architecture, and the technical quality of what the team builds.

Core responsibilities:

Architecture decisions. Choosing the right patterns, technologies, and approaches for the problems the team is solving. Writing or sponsoring RFCs for significant technical decisions.
Code quality. Setting standards for testing, code review, documentation. Being the final reviewer on complex changes. Not writing every line of code themselves, but ensuring the codebase maintains a level of quality that the team can sustain.
Technical mentorship. Helping engineers grow their technical skills. Pairing on hard problems. Explaining the reasoning behind architectural decisions so the team learns the "why," not just the "what."
Technical risk management. Identifying technical debt, performance risks, scalability limits. Communicating these to leadership in business terms. "Our current database schema won't support the multi-tenancy feature on the roadmap without a migration that will take 4-6 weeks."
Unblocking the team technically. When an engineer is stuck on a hard problem, the Tech Lead dives in. When a third-party API is behaving unexpectedly, the Tech Lead debugs it. They're the technical backstop.

What the Tech Lead does not do: performance reviews, career development conversations, salary negotiations, hiring decisions (though they participate in technical interviews), or process management.

The Tech Lead's primary output is technical decisions and technical quality. They succeed when the team builds things the right way.

The Engineering Manager role

The Engineering Manager owns the people and process dimension of the team. Their domain is the humans, the workflows, and the organizational context the team operates in.

Core responsibilities:

People management. One-on-ones, performance reviews, career development, feedback, conflict resolution. Understanding what motivates each person on the team, what frustrates them, and what they need to grow.
Hiring and team composition. Defining what roles the team needs, running the hiring process, making hiring decisions. Building a team with the right mix of skills, experience levels, and perspectives.
Process and delivery. Sprint ceremonies (if using Scrum), workflow optimization, removing organizational blockers. Ensuring the team has a process that works and isn't drowning in meetings.
Stakeholder management. Translating business priorities into team priorities. Managing expectations with product, design, and leadership. Shielding the team from context-switching and scope creep.
Team health. Monitoring workload, preventing burnout, ensuring psychological safety. Noticing when someone is disengaged and addressing it before it becomes a resignation.

What the Engineering Manager does not do: make architecture decisions, be the final arbiter of code quality, or be the deepest technical expert on the team. They should be technical enough to understand what the team builds and have informed conversations about trade-offs, but their job is not to be the best engineer in the room.

The Engineering Manager's primary output is a healthy, productive, growing team. They succeed when the team delivers consistently and the people on it are developing in their careers.

Why conflating them fails

When one person does both, something gives. Always. Here's what I've seen:

Scenario 1: The technical leader who hates managing people. This is the most common. A brilliant engineer becomes "the lead" and now has to do one-on-ones, performance reviews, and hiring. They skip the one-on-ones ("I'm too busy"), give vague performance feedback ("you're doing fine"), and hire based purely on technical skill without evaluating team fit. The team's code is excellent. The team's morale is terrible. People leave, and the lead is confused because "we have such interesting technical problems."

Scenario 2: The people-oriented leader who loses technical credibility. Less common but equally damaging. A manager who's great with people but stops staying current technically. The team likes them personally but doesn't trust their technical judgment. Architecture decisions get made by the loudest senior engineer instead of through structured evaluation. Technical debt accumulates because the manager doesn't recognize it or can't prioritize it credibly.

Scenario 3: The burned-out hybrid. The person who genuinely tries to do both and works 60-hour weeks to make it happen. They do a decent job at both for a while -- until they burn out. And when they leave, the team loses both functions simultaneously, which is catastrophic.

When one person can do both

There's a phase where combining the roles makes sense: very early stage, typically a team of 2-5 engineers.

At this size, the "management" overhead is minimal. One-on-ones are informal. There's no complex process to manage. Hiring happens rarely. The person needs to be technically strong and emotionally intelligent, but the people management load is light enough that one person can carry both without sacrificing either.

The signals that it's time to split:

Team size exceeds 6-7 engineers. Beyond this, the people management load is a full-time job. One-on-ones alone take 3-4 hours per week. Add hiring, performance reviews, and stakeholder management, and there's no time left for architecture work.
The combined lead is consistently behind on one dimension. One-on-ones keep getting cancelled. Or architecture reviews aren't happening. Something is being sacrificed.
The team has engineers at different career stages. A team of all seniors needs less management. A team with juniors, mids, and seniors needs active career development, mentoring structures, and differentiated feedback -- that's real management work.
Technical complexity is increasing. If the system is growing in scope and the architecture decisions require deep, focused thought, the Tech Lead needs time that people management doesn't leave them.

Structuring both roles (15-40 person org)

In a 15-40 person engineering organization, here's a structure that works:

Engineering Managers own teams of 5-8 engineers. Each EM is responsible for people, process, and delivery for their team. They report to a VP of Engineering or Head of Engineering.

Tech Leads are embedded within teams. Each team has a Tech Lead who owns technical direction. The Tech Lead is a peer of the EM, not a subordinate. They collaborate: the EM sets the "what" and "when" (based on business priorities), the Tech Lead sets the "how."

Key relationship: EM and Tech Lead are partners, not a hierarchy. The EM doesn't override technical decisions. The Tech Lead doesn't override people decisions. When they disagree, they resolve it between themselves or escalate to their shared manager. This partnership model requires mutual respect and clear communication, but when it works, it's powerful.

Staff/Principal Engineers operate across teams. For organizations on the larger end (30+), Staff Engineers provide cross-team technical leadership -- ensuring consistency across systems, driving platform-level decisions, and mentoring Tech Leads. They don't manage people. They're on the technical track, at a higher level of scope.

Career paths

This is where many organizations fail. If Tech Lead is the only path to career growth, you're forcing great engineers into management they don't want. If Engineering Manager is the only path, you're losing technical depth at the leadership level.

The technical track: Senior Engineer -> Staff Engineer -> Principal Engineer -> Distinguished Engineer / Fellow

At each level, the scope increases. A Senior Engineer leads within a project. A Staff Engineer leads across a team. A Principal Engineer leads across the organization. Impact grows through technical influence, not people management.

The management track: Senior Engineer -> Engineering Manager -> Senior EM / Director -> VP of Engineering

At each level, the organizational scope increases. An EM manages one team. A Director manages multiple teams. A VP manages the function. Impact grows through organizational effectiveness and people development.

The critical point: both tracks must have equivalent compensation and prestige. If your Staff Engineers make less than your Directors, or if your culture implicitly treats management as the "real" career, your technical track is a fiction and your best engineers will either leave or reluctantly become mediocre managers.

How to transition

If you currently have hybrid lead/manager roles and want to split them:

Identify which dimension each current lead gravitates toward. Most people have a natural preference. The lead who loves architecture discussions and pair programming? Tech Lead. The lead who's great at one-on-ones and hiring? EM.
Don't force transitions. If a current lead wants to stay hybrid and the team is small enough to support it, that's fine. The split should happen because the team needs it, not because an org chart says so.
Define the roles clearly and communicate them. The team needs to know who to go to for what. "Talk to Alex about architecture decisions. Talk to Jordan about career growth and process."
Give it a quarter to settle. Role transitions are awkward. The former hybrid lead who's now "just" a Tech Lead may feel like they lost status. The new EM may feel uncertain about their authority. Give it time and actively support both people through the transition.

At Conectia, we work with engineering organizations at every stage of this evolution. Some of our clients have a single lead running everything, others have mature EM/TL splits. Our senior engineers integrate into either structure -- they bring the technical depth of a strong IC who can partner with both Tech Leads and Engineering Managers. Because the best teams aren't defined by their org chart. They're defined by clarity of roles and quality of people.

Scaling your engineering team and need senior engineers who fit into your structure from day one? Talk to a CTO -- our senior LATAM engineers bring the technical maturity that both Tech Leads and Engineering Managers want on their team.