Two Distinct but Complementary Roles
One of the most common sources of confusion in engineering organizations is the distinction between a Tech Lead and an Engineering Manager. While both are leadership roles, they have fundamentally different accountability domains. The Tech Lead owns the what and how of technical execution, while the Engineering Manager owns the who and why of team health, growth, and organizational alignment.
In practice, these roles form a partnership. The best engineering teams have a strong Tech Lead and a strong Engineering Manager working in tandem, each respecting the other's domain while collaborating on shared goals like delivery, team culture, and hiring.
Role Comparison
| Dimension | Tech Lead | Engineering Manager |
|---|---|---|
| Primary Focus | Technical direction and quality | People, process, and delivery |
| Reports | Usually no direct reports | Has direct reports |
| Coding Time | 30-70% of time | 0-20% of time |
| Meetings | Design reviews, tech syncs | 1-on-1s, skip-levels, cross-team |
| Career Path | Staff / Principal Engineer | Senior EM / Director / VP Eng |
| Hiring Focus | Technical assessment | Culture fit, team composition |
| Performance Reviews | Provides technical input | Owns the review process |
| Decision Authority | Architecture, tech stack, standards | Team structure, process, priorities |
The Tech Lead's Domain
The Tech Lead is accountable for technical excellence. This includes architectural decisions, code quality standards, technical debt management, system reliability, and ensuring the team builds the right thing in the right way. The Tech Lead is expected to be the strongest technologist on the team or one of the strongest, and to use that expertise to guide and elevate others.
- Designs system architecture and writes RFCs for major changes
- Sets and enforces coding standards through code review
- Makes technology and tooling decisions
- Identifies and prioritizes technical debt
- Mentors engineers on technical skills
- Prototypes and spikes risky technical approaches
- Acts as the escalation point for hard technical problems
The Engineering Manager's Domain
The Engineering Manager is accountable for the people and the process. This includes hiring, performance management, career development, team morale, cross-team coordination, and ensuring the team has the resources and context needed to succeed. The EM shields the team from organizational noise and creates the conditions for engineers to do their best work.
- Conducts regular 1-on-1s focused on career growth and well-being
- Writes and delivers performance reviews
- Manages headcount planning and hiring pipeline
- Handles conflict resolution and team dynamics
- Aligns the team's work with organizational strategy
- Manages stakeholder relationships and expectations
- Removes organizational and process blockers
Where the Roles Overlap
Despite distinct domains, there are significant areas of overlap that require close collaboration:
Shared Responsibilities
- Sprint Planning: The TL defines technical scope and complexity; the EM ensures alignment with team capacity and organizational priorities
- Hiring: The TL designs technical interviews and evaluates candidates' skills; the EM manages the pipeline, makes offers, and evaluates culture fit
- Onboarding: The TL provides technical onboarding (codebase, architecture); the EM provides organizational onboarding (processes, relationships)
- Delivery: Both are accountable for the team shipping quality work on time, but from different angles
- Team Culture: Both contribute to engineering culture through their actions and expectations
The Tech Lead Manager (TLM) Hybrid
Some organizations, notably Google, use a Tech Lead Manager model where one person fills both roles. This works best for small teams (3-5 engineers) where the overhead of two separate leadership roles is not justified. However, the TLM model has significant downsides as teams grow: the person inevitably skews toward one domain at the expense of the other, and the cognitive load of managing both people and technology becomes unsustainable.
When to Split the Roles
Consider splitting the TLM into separate Tech Lead and Engineering Manager roles when:
- The team grows beyond 5-6 engineers
- The technical complexity of the system increases substantially
- The TLM consistently drops balls on either the people or technical side
- Performance reviews and career development conversations are being deprioritized
- There is not enough time for both deep technical work and management duties
Communication Patterns Between TL and EM
The most effective TL-EM partnerships establish clear communication patterns:
- Weekly sync: A dedicated 30-minute meeting to discuss team health, delivery status, and upcoming priorities
- Shared context: The TL keeps the EM informed about technical risks; the EM keeps the TL informed about organizational changes
- United front: Disagreements are resolved in private; the team sees a consistent message from both leaders
- Complementary feedback: The TL provides technical growth feedback; the EM incorporates it into performance reviews alongside behavioral and impact feedback
Choosing Your Path
If you are an experienced engineer considering which direction to take, consider these questions:
- Do you get more energy from solving technical problems or from growing people? Tech leads lean technical; EMs lean toward people.
- Are you comfortable giving up most of your coding time? EMs write very little code. If that prospect makes you uncomfortable, the TL path may be better.
- Do you enjoy organizational strategy and politics? EMs navigate organizational dynamics daily.
- Do you want to design systems that scale to millions of users? The staff/principal engineer path preserves deep technical focus.
Key Takeaway
The Tech Lead and Engineering Manager are complementary roles that together cover the full spectrum of engineering leadership. The best teams have both roles filled by strong individuals who communicate openly, respect each other's domain, and share accountability for the team's success. Neither role is "above" the other; they are peers with different areas of focus.