Roles guide
Tech Lead vs Engineering Manager: what’s the difference?
Published
The Tech Lead is accountable for a team’s technical direction: architecture, quality, technical choices, delivery. The Engineering Manager is accountable for the people: hiring, one-on-ones, career growth, organisation. In a small company one person often wears both hats; as the team grows, splitting them keeps either one from being neglected.
| Topic | Tech Lead | Engineering Manager |
|---|---|---|
| Main focus | The system: architecture, code, production | The people: team, careers, organisation |
| Typical decisions | Technical choices, standards, boundaries, debt | Hiring, staffing, process, promotions |
| Reporting line | Usually none | Direct manager of the team |
| Share of coding | Real, off the critical path | Low or none |
| Rituals | Code and architecture reviews, written decisions | One-on-ones, performance reviews, hiring |
| Signs of success | Regular releases, stable production, debt under control | An engaged team that grows and stays |
| Common next steps | Staff or Principal Engineer, architect, CTO | Head of Engineering, VP Engineering, CTO |
Two roles, two focuses
The Tech Lead looks at the system. Will the architecture hold the next feature, is quality slipping, is production under control?
The Engineering Manager looks at the people. Is everyone growing, does the team have the right size and the right profiles, is someone quietly checking out?
Both questions matter equally. A team can have a clean architecture and lose its best people, or the other way round.
Where the roles overlap
Hiring: the Engineering Manager runs the process, the Tech Lead assesses the technical level, ideally on real code.
Onboarding: the Tech Lead prepares the environment and the first ticket, the Engineering Manager makes sure the person finds their place.
Culture: both carry it, each with their own tools.
When one person wears both hats
In a startup or a small team, this is the most common case. The risk is well known: the urgent hat eats the other one. A production incident pushes back the one-on-ones, a hiring round pushes back the architecture review.
To make it last, block fixed time for each hat and write your technical decisions down so they survive your busy weeks. Keep the team small too; adding people adds coordination.
Related principles
When to split the roles
The signs are familiar: one-on-ones get skipped, technical decisions drag on, the same person is pulled in every direction. Once the organisation grows to several teams, the question becomes structural.
Architecture tends to mirror the organisation that builds it. Splitting teams along the target architecture, then giving each one a Tech Lead and a clear management line, holds up better than the reverse.
Which one to choose for your career
Ask yourself a simple question: what gives you energy at the end of the week? Having cracked a hard technical problem, or having watched someone on the team reach a new level?
Both tracks lead to leadership positions. Nothing is final: many people alternate, and a stint in management often makes a better Tech Lead.
Related principles
Making the pair work
A Tech Lead and Engineering Manager pair works when each knows what they decide alone and what they decide together. Write it down. A clear frame gives freedom, grey areas create conflict.
Share context continuously. Two people aiming at the same goal with different information end up distrusting each other.
Related principles
Frequently asked questions
- Is the Tech Lead the team’s manager?
- Not necessarily. In most organisations, the Tech Lead owns technical direction without a reporting line; performance reviews, salaries and career growth belong to the Engineering Manager. In a small company, one person can hold both roles.
- Who is senior, the Tech Lead or the Engineering Manager?
- Neither, by nature. They are often peers with different scopes: the Tech Lead settles technical topics, the Engineering Manager settles team and organisation topics. The exact reporting structure depends on the company.
- Does an Engineering Manager need to know how to code?
- They need to understand technical work to hire, assess and arbitrate well. Developer experience helps a lot; coding day to day is usually not expected.
- Can you move from Tech Lead to Engineering Manager, and back?
- Yes. They are two distinct tracks and moving back and forth is common. Time in management builds listening and organisational skills that help a Tech Lead later.
- What is the difference between a Tech Lead, a Staff Engineer and an architect?
- The Tech Lead owns the technical direction of one team. A Staff Engineer has technical influence beyond a single team. An architect looks after the overall consistency of the information system. Job titles vary between companies.
Other guides
The 60 principles, in one book
Every principle cited in these guides is covered in NoBullshit Tech-Lead: 240 pages for developers, Tech Leads, architects and CTOs (in French).