When to Hire an Engineering Manager vs. a Tech Lead

When my team grew to 9 engineers, I knew I needed help. I was spending all my time in 1:1s, performance discussions, and coordination meetings. I had no bandwidth for technical direction. But I faced a choice: hire an engineering manager to handle the people side, or hire a tech lead to handle the technical side?

I initially hired a tech lead. It was the wrong call. Not because tech leads are less valuable—but because the team's primary bottleneck was people leadership, not technical direction. The tech lead was excellent, but the team still came to me for career conversations, conflict resolution, and project prioritization. I'd hired for the wrong gap.

That mistake taught me a framework for this decision that I've used successfully ever since.

Understanding the Two Roles

First, let me be clear about what these roles actually do in practice, because titles vary enormously across companies:

Responsibility	Engineering Manager	Tech Lead
1:1s and career development	Primary owner	Supporting role
Performance reviews	Primary owner	Provides technical input
Hiring and interviewing	Primary owner	Technical assessment
Sprint planning and prioritization	Co-owner with PM	Technical complexity input
Architecture decisions	Informed, not deciding	Primary owner
Code review and standards	Light involvement	Primary owner
Cross-team technical alignment	Stakeholder	Driver
Team process design	Primary owner	Input and adoption
Incident response	Coordination	Technical leadership
Conflict resolution	Primary owner	Involved when technical

The overlap is significant, which is why many smaller teams combine the roles. But as teams grow, the combined responsibilities exceed one person's bandwidth.

The Decision Framework

I use three questions to determine which role to hire first:

Question 1: What is the team's primary bottleneck? If the bottleneck is people-related (retention risk, unclear career paths, interpersonal friction, process problems), hire an EM. If the bottleneck is technical (inconsistent architecture, quality problems, no technical direction, design reviews piling up), hire a tech lead.

Question 2: What is the existing leader spending too much time on? If you're spending all your time on people management and technical direction is suffering, you need a tech lead to offload the technical side. If you're spending all your time on architecture and individuals are feeling neglected, you need an EM.

Question 3: What does the team need in 12 months? Teams' needs evolve. A team that needs technical direction now might need people leadership in 6 months as it grows. Hire for where the team is heading, not just where it is today.

When You Need an Engineering Manager

Signals that people leadership is your gap:

• Retention risk: Engineers are disengaged, updating resumes, or not growing
• Interpersonal friction: Unresolved conflicts between team members affecting collaboration
• Process chaos: No clear sprint cadence, unclear priorities, constant firefighting
• Growth stagnation: Engineers aren't developing new skills or expanding their scope
• Manager burnout: You're doing people management on top of everything else and dropping balls
• Team size > 7 without dedicated people leader: At this size, individual attention becomes impossible without help

An EM handles the human infrastructure: making sure people feel supported, growing in their careers, resolving conflicts, and maintaining sustainable processes. Without this, even the best technical direction fails because people leave or disengage.

When You Need a Tech Lead

Signals that technical leadership is your gap:

• Architectural drift: Services are designed inconsistently, making the system harder to understand
• Quality problems: Increasing incidents, bug escape rate, or technical debt accumulation
• Design bottleneck: You're the only reviewer for significant technical decisions and it's slowing everything
• Junior-heavy team: The team has many growing engineers who need technical mentorship and guidance
• Cross-team technical work: Major infrastructure or platform initiatives need a dedicated technical driver
• No technical vision: The team builds feature by feature without a cohesive technical strategy

A tech lead provides the technical north star: ensuring the codebase evolves coherently, that architecture decisions are made thoughtfully, and that the team's technical standards continuously improve.

The Dual-Role Trap

Many companies try to save headcount by combining EM and Tech Lead into one role—the "TLM" (Tech Lead Manager). This can work in specific circumstances:

TLM works when:

• Team is 4-6 people
• Technical challenges are moderate (not rebuilding core systems)
• The individual is genuinely strong at both people and technical leadership
• The team is relatively senior and self-directed

TLM fails when:

• Team exceeds 6-7 people (both halves of the role get shortchanged)
• Major technical challenges require full-time architectural thinking
• The individual is strong at one and adequate at the other (adequate isn't enough for either role)
• The team has high people-leadership needs (many juniors, interpersonal issues, career development demands)

In my experience, the TLM role is a transitional state. It works for a period but eventually splits as the team grows. Plan for the split rather than pretending it won't be needed.

Structuring the Relationship

When you have both an EM and a Tech Lead, their working relationship determines team health. I've seen three models:

Model 1: EM is manager, TL is senior IC The EM manages everyone including the TL. The TL has authority over technical decisions but reports to the EM. Works well when the EM has strong technical background.

Model 2: Both report to the same director EM and TL are peers, both reporting to a director or VP. EM owns people and process; TL owns technical direction. Works well when clear boundaries are maintained.

Model 3: TL reports to EM, but with explicit authority boundaries The EM manages the TL but explicitly delegates technical decision-making authority. The TL doesn't need EM approval for technical choices.

I prefer Model 2 for larger organizations and Model 3 for smaller ones. The critical success factor regardless of model: both must respect the other's domain and collaborate rather than compete for influence.

Common Failure Patterns

Patterns I've observed when the EM/TL relationship goes wrong:

• Territory wars: EM and TL compete over who "owns" the team rather than serving it together
• Confused reports: Engineers don't know who to go to for what, getting conflicting guidance
• Absent technical voice: EM makes all decisions including technical ones, marginalizing the TL
• Absent people voice: TL runs the team as a technical project, ignoring growth, morale, and sustainability
• Status mismatch: One role is clearly higher-status, making the other feel subordinate

Each of these requires intervention. The EM/TL pairing needs explicit discussion of responsibilities, regular alignment meetings, and a shared understanding that both roles are equally essential.

Key Takeaways

• Determine your primary bottleneck: people-related gaps need an EM, technical gaps need a tech lead
• Consider what the existing leader spends too much time on—hire to offload that
• The TLM (combined) role works for teams of 4-6 but eventually needs to split
• When you have both, structure clear authority boundaries and mutual respect between the roles
• Hire for where the team will be in 12 months, not just today's problems
• The relationship between EM and TL must be actively maintained—regular alignment and clear domains
• Neither role is more important—teams need both people infrastructure and technical direction to thrive
• If you can only hire one, choose based on which gap causes more acute damage to the team right now

The EM/TL decision isn't permanent. Teams evolve, and what was right six months ago may not be right today. Revisit the question regularly and be willing to restructure as needs change.