AI, data & engineering
Engineering Manager
Engineering Manager is the leader of an engineering team, responsible for people, hiring and steady delivery, sharing technical decisions with a Tech Lead.
Also known as: EM, Software Engineering Manager, Engineering Lead, Development Manager, Team Lead, Senior Engineering Manager.
What does an Engineering Manager do?
An Engineering Manager is the leader of an engineering team, responsible for who works in it, how people grow and how the team ships the product on time without losing quality. Technical decisions usually stay with strong engineers. Typical tasks:
- hire engineers, onboard them and build a development plan for each;
- run one-on-ones, give feedback and deal with performance and motivation problems;
- agree priorities and timelines with the Product Manager and shield the team from unnecessary work;
- set up delivery: planning, releases, incident reviews, handling technical debt;
- in the player-coach model, write code and review it themselves, usually part of the time.
When does a company need an Engineering Manager?
A company needs an Engineering Manager when a team has grown to the point where the strong engineer leading it can no longer keep up with both writing code and looking after people. Common triggers: the CTO is drowning in one-on-ones and interviews, hiring is about to speed up, several teams need a management layer below the CTO, releases slip. While there are only one or two small teams, a company usually needs a player-coach — an Engineering Manager who spends a significant share of time writing code and shaping the architecture. The role will not work if the team is small and the main problem is technical: then you need a strong Tech Lead or a Staff Engineer.
Engineering Manager vs Team Lead and Tech Lead: what's the difference?
An Engineering Manager is primarily responsible for people and delivery, while a Tech Lead is responsible for the team's technical decisions. Team Lead means different things in different companies, but most often it is a mix of the two: a leader who both writes code and manages people, in effect a player-coach Engineering Manager. What sets an Engineering Manager apart from a CTO / VP Engineering is scale: an Engineering Manager runs a team, a VP Engineering runs managers and the whole engineering organisation, and a CTO also owns technology strategy.
Engineering Manager vs related roles: comparison
| Engineering Manager | Tech Lead | CTO / VP Engineering | |
|---|---|---|---|
| Responsible for | The team's people, hiring and delivery | The team's technical decisions | All of the company's engineering |
| Writes code | Partly, in the player-coach model | Yes, most of the time | Rarely |
| Reports | Engineers | Usually none | Engineering Managers, heads of areas |
Why is it hard to hire an Engineering Manager?
Engineering Managers are hard to hire because they need to remain strong enough engineers for the team to trust them, and such people often choose a technical career over a management one.
- Titles are used inconsistently: EM, Team Lead and Tech Lead mean different things in different companies, and the same line in a CV hides very different experience.
- Management results are hard to see in a CV: "led a team of eight" does not say who grew in it, who left and whether delivery got better.
- Companies want a player-coach, while candidates are usually strong in one half: either they have not written code for a long time, or they manage people as an afterthought.
What to decide before hiring an Engineering Manager?
- How much code: player-coach or pure management? Half the time in code plus full ownership of people gives you neither — name the share upfront.
- Who makes technical decisions in the team? If there is no strong Tech Lead, the Engineering Manager will have to cover that too, and the profile changes.
- How is responsibility split with the Product Manager and the CTO? Without a clear boundary the EM either becomes a second Product Manager or loses influence over priorities.
Where to find an Engineering Manager?
Engineering Managers most often come from product companies with an established engineering culture and a separate management track: large technology companies, mature startups, fintech, e-commerce. Player-coaches are more often found in small startups, where the team lead remains one of the strongest engineers. A strong signal is people the candidate hired and grew, and a concrete story of how the team's delivery changed under them. NEWHR finds such candidates by the results of their work, not by applications to a job post.
How to assess an Engineering Manager in an interview?
Engineering Managers are assessed with a behavioural interview on real situations from their practice and a case about the company's team, plus a technical interview for a player-coach. On the company side, the CTO or VP Engineering takes part, along with the Product Manager they will work with.
Strong signals:
- talks about specific people: whom they grew, whom they parted with and why;
- describes delivery through the team's results, not through process for its own sake;
Red flags:
- every success is a personal technical achievement, and the team is mentioned in passing;
- cannot recall a single difficult conversation with a report;
- describes management through control: reports, time tracking, micromanagement.
How long does it take to hire an Engineering Manager?
We present the first candidates for the Engineering Manager role within 5–7 days of the brief.
Related roles
- CTO / VP Engineering — the next level up: if engineering has no leader at all, hire one first, and Engineering Managers follow.
- Staff Engineer — the senior track without reports; the right hire when the team's problem is architecture, not people.
- Product Manager — the Engineering Manager's closest partner, owning what the team builds and why.
- Founding Engineer — in a team of a few people, a more useful first hire than an Engineering Manager.