The engineering manager and tech lead roles are frequently confused, often combined, and sometimes set in opposition to each other. This guide clarifies the distinct responsibilities of each role, explains how they complement each other, and helps you decide which path aligns better with your strengths.
Defining the Roles Clearly
The engineering manager is responsible for people. They own hiring, performance management, career development, one-on-ones, team culture, and stakeholder communication. Their primary accountability is the health and effectiveness of their team — both the humans and the processes that connect them.
The tech lead is responsible for technical direction. They own architecture decisions, code quality standards, technical debt strategy, design reviews, and technical mentoring. Their primary accountability is the quality and sustainability of the team's technical output.
In practice, the boundary between these roles is rarely clean. Both roles influence team dynamics, both contribute to delivery, and both require strong communication skills. The distinction lies in primary accountability: the engineering manager is ultimately accountable for people outcomes, and the tech lead is ultimately accountable for technical outcomes.
How Daily Work Differs
An engineering manager's day is dominated by conversations. One-on-ones, team meetings, stakeholder syncs, hiring discussions, and cross-functional alignment fill the calendar. The remaining time goes to performance reviews, planning, and staying connected with the team's work. Most EMs spend less than ten per cent of their time on hands-on technical work.
A tech lead's day blends technical work with coordination. They write code, review pull requests, participate in design discussions, and make architectural decisions. They also coordinate with the engineering manager on priorities, mentor other engineers on technical topics, and represent the team's technical perspective in planning discussions. Most tech leads spend fifty to seventy per cent of their time on technical work.
The emotional weight of the roles also differs. Engineering managers carry the emotional burden of their team members' well-being, career anxieties, and interpersonal dynamics. Tech leads carry the intellectual burden of technical decisions — the pressure of making architecture choices that will shape the codebase for years. Both types of burden are real; they simply manifest differently.
How the Roles Complement Each Other
The most effective engineering teams have a strong partnership between the engineering manager and the tech lead. The EM ensures the team is staffed, motivated, and aligned with organisational goals. The tech lead ensures the team's technical work is sound, sustainable, and well-architected. Together, they cover the full spectrum of team needs.
Communication between the EM and tech lead should be frequent and candid. They need to align on priorities, share observations about team dynamics, and coordinate on feedback for individual engineers. A weekly sync dedicated to team health and strategy — not just delivery status — is a worthwhile investment.
The partnership works best when both roles respect each other's domain. The EM should not override technical decisions without strong justification. The tech lead should not make management decisions (hiring, performance ratings, team structure) without the EM's involvement. Clear boundaries create mutual respect and prevent the friction that arises when roles overlap excessively.
When the Roles Are Combined
At smaller companies, the engineering manager and tech lead roles are often combined into a single position. This can work effectively when the team is small (four to six engineers) and the technical complexity is manageable. The combined role offers the advantage of unified decision-making — one person understands both the people and technical dimensions of every situation.
The risk of combining the roles is that one dimension inevitably suffers. Most people have a natural orientation toward either people leadership or technical leadership, and under pressure, they default to their strength. A technically-oriented combined EM-TL may neglect one-on-ones and career development. A people-oriented combined EM-TL may disengage from code reviews and architecture decisions.
If you are in a combined role, be honest about which dimension gets less of your attention and create systems to compensate. If you tend to neglect people work, block calendar time for one-on-ones and make them non-negotiable. If you tend to neglect technical work, schedule regular code review sessions and architecture discussions. Awareness of your blind spot is the first step to managing it.
Choosing Between the EM and Tech Lead Paths
If you are deciding between the engineering manager and tech lead paths, consider where your energy naturally flows. When your team ships a successful project, do you feel proudest of how the team collaborated and grew, or of the technical elegance of the solution? When you have a free hour, do you gravitate toward a one-on-one conversation or a code review? These instinctive preferences are strong signals about which role will feel sustainable over the long term.
Career progression differs between the paths. The tech lead path typically leads to staff engineer, principal engineer, and distinguished engineer roles — deepening technical impact with each step. The EM path leads to senior EM, director, and VP roles — broadening organisational impact with each step. Both paths offer equivalent progression at well-run companies, but the nature of advancement is fundamentally different.
You can switch between the paths. Many successful engineering leaders have held both tech lead and EM roles at different points in their career. The experience of each role enriches the other — tech leads who have managed people understand the human dimension of technical decisions, and EMs who have led technically understand the constraints and trade-offs their teams navigate.
Key Takeaways
- The EM owns people outcomes; the tech lead owns technical outcomes — clear boundaries create mutual respect
- Daily work differs: EMs are conversation-driven, tech leads blend technical work with coordination
- The strongest teams have a robust partnership between EM and tech lead with frequent, candid communication
- Combined roles can work for small teams but risk neglecting one dimension under pressure
- Choose based on where your energy flows and what type of impact you find most satisfying
Frequently Asked Questions
- Is the tech lead role a step toward engineering management?
- It can be, but it is not necessarily. The tech lead role is a leadership position on the IC track, and many tech leads advance to staff and principal engineer roles without ever entering management. However, the tech lead role does develop several skills that are directly transferable to management — team coordination, stakeholder communication, and decision-making under ambiguity. If you are interested in management, a tech lead role is an excellent way to test your appetite for leadership while maintaining a strong technical base.
- Who has more authority — the engineering manager or the tech lead?
- The engineering manager has more formal authority — they make hiring decisions, write performance reviews, and influence compensation. The tech lead has more technical authority — they make architecture decisions, set code quality standards, and determine technical approaches. In practice, the most effective teams operate through collaboration rather than authority. The EM and tech lead influence each other's domains through conversation and mutual respect, not through pulling rank.
- Can I be both engineering manager and tech lead permanently?
- For small teams (four to six engineers), this can work long-term. Beyond that size, the combined workload becomes unsustainable and both dimensions suffer. If your team is growing beyond six people, start planning to split the roles. Identify a strong senior engineer who can grow into the tech lead position and begin delegating technical leadership responsibilities to them.
Read the EM Field Guide
Whether you are an EM, tech lead, or considering either path, our field guide covers the frameworks and practices that make engineering leaders effective in any role.
Learn More