When to hire your first engineering manager (and what changes with contractors on the team)

When to hire an engineering manager comes down to one test: hire when coordination and people work, not headcount, eat the senior person's week. For most teams that lands somewhere between 8 and 15 engineers, but the number is a heuristic, not a law. If your best engineer or CTO spends more time on 1:1s, hiring loops and unblocking people than on technical direction, you're already late.

What a tech lead does and how a career ladder works sit in our engineering management guides for CTOs and VPs of Engineering.

What is the real trigger: headcount or coordination load?

Every page that ranks for this question gives a different number. Recruiter open-source.io says 6-10 engineers. Abdelrahman Algazzar's growth-stage framework puts the inflection at 8-14, with 15+ needing more than one manager. Coach Lena Reinhard says 10-20. None of them publishes data behind the range, and Algazzar calls his thresholds a starting point, not a formula. Treat all three as opinions from people who sell advice or recruiting, which is a fair description of most of the genre.

Our judgment: the spread tells you headcount is a weak trigger. Two teams of 12 can need very different amounts of management depending on seniority, how many projects run in parallel, and how much the lead still codes. The load is what counts.

So measure it. Have your senior lead (or yourself) log time for two weeks: 1:1s, standups, hiring loops, unplanned help, status conversations. Algazzar's rule of thumb is that 15-20 hours a week on this work means you have a management gap. That's his rule of thumb, not a study, but it's a better tiebreaker than a headcount band because you can check it on Friday.

Five signals you can check this week

Open-source.io's advice is to hire just before the strain, not after. By the time these signals are obvious, you've usually been paying for the gap for a quarter.

1. Span of control past 6-8 reports

Algazzar's FAQ puts a healthy span at 6-8 direct reports, and 4-6 for a player-coach who still writes code. If the CTO has 10 people reporting directly and also owns architecture, something is already getting dropped.

2. 1:1s are skipped or shortened

Count how many 1:1s moved or got cut to 15 minutes last month. Skipped 1:1s are the earliest signal because they're the first thing to go when a lead is busy, and the damage shows up months later as attrition.

3. Nobody owns people issues

Who gives feedback on a weak quarter? Who talks to the engineer who wants to grow into a staff role? Who runs the hiring process end to end? Open-source.io lists "no owner for people issues" among its core signals. If the honest answer is "whoever notices", you need an owner.

4. The founder or lead is the bottleneck

When every decision and every tricky code review routes through one person, throughput is capped by their calendar. Open-source.io names the founder or lead as bottleneck as a clear trigger.

5. Heavy hiring ahead

Reuben Roth's LinkedIn piece lists more than five critical roles to fill in a year as a signal. Hiring is a second job. Someone has to run sourcing, interviews and onboarding, and it's rarely a person who also ships features.

Two or three of these at once is a hire-now situation. One alone usually isn't.

Too early: when a senior or staff engineer is the better first move

Open-source.io says hiring a manager for a team of three is a mistake, and that a senior or staff engineer is the better choice. Algazzar says to stay flat below 8. Both fit what we see: a manager hired into a team of five has little to manage, and they either meddle in technical work or sit idle. Neither outcome is their fault.

The better first move at that size is usually someone who raises the technical ceiling and can act as tech lead. What a tech lead owns and what to hand off is covered separately, including where the split with a manager sits.

Engineering manager vs tech lead vs senior engineer

The roles overlap on small teams, which is part of why the timing question is confusing. Roughly:

Role	Owns	Typical first-hire case
Engineering manager	People: hiring, feedback, growth, team health, delivery process	Coordination and people work are eating the senior lead's week
Tech lead	Technical direction: architecture, code standards, how it gets built	The team needs technical decisions made, not more people management
Senior or staff engineer (IC)	Hard technical work and mentoring, no direct reports	Team of about 3-7 that needs depth more than structure

The tech lead article frames the split as who does the work versus how it gets built. An engineering manager sits on the first half. A tech lead sits on the second. A senior IC does neither full time.

Promote a tech lead or hire externally?

Charity Majors argued in a 2021 LeadDev piece that management is a career change, not a promotion. She puts the bar for an internal candidate at roughly 5-7 years of hands-on engineering. Our advice on top of that: make sure they actually want it. If your best engineer is just the strongest coder, promoting them to manager costs you a great engineer and may give you a reluctant manager. Ask them. Then ask again in three months.

Internal promotion skips learning the codebase and the people, but Reinhard still puts effectiveness at 3-6 months, against 3+ months for an external hire. Algazzar says an external hire needs 60-90 days to ramp.

Majors gives several cases for going external, including a team of mostly early-career engineers where the seniors don't want to manage. We'd add the plain case of no experienced, willing candidate.

On cost, the only salary data we found is in dollars. RecruitsLab's 2026 bands put base pay for a first-time engineering manager at $180K-230K, rising to $220K-280K at 3-5 years and $260K-340K at 5+. We found no Europe-specific figure from a source we'd trust, so we won't guess one. Pay varies a lot by country, and a local salary survey or a conversation with a recruiter in your market beats an extrapolation from dollar bands.

One more disagreement worth knowing: how much a player-coach should still code. Algazzar says 40-60%. RecruitsLab says 20-30% for a single feature team. The honest answer is that it depends on span, and a manager with six reports who codes half the time is mostly a senior engineer with extra meetings.

What changes when part of the team is contractors or nearshore

None of the pages we read cover this, and it's a common setup for growing teams. The following is our judgment, not sourced data.

Contractors still need a day-to-day owner. The difference is what that owner does. For employees, a manager runs performance reviews and career growth, which is why where contractors fit on the ladder is a separate question from the one this article asks. For contractors, the job is delivery: priorities, onboarding, review turnaround and integration into the team's rituals. That's lighter than full people management, so a team with a high contractor share can wait a little longer for its first EM.

There's a limit. A dedicated external team with its own tech lead can defer the EM hire, but only if someone in-house owns priorities and code review. Our agile team structure guide gives a floor of two in-house anchors for every team of up to nine, and that floor still applies. If your in-house group has dropped below it, a manager is a more urgent hire, not a less urgent one.

The cheaper way to buy time is to add senior ICs first. HighCircl matches engineers within 72 hours, with a shortlist of 3-5 candidates and no minimum hour commitment, so you can test whether more seniority fixes the coordination problem before committing to a permanent hire with a 4-7 week search ahead (RecruitsLab's figure). If it doesn't, you've lost little. If you're also deciding what order to fill roles in, the first-hires order after a Series A covers the sequence.

What this means for your team shape

Your decision is one of three: hire a manager now, promote a tech lead, or add senior ICs and defer.

Run the two-week time log first. If your senior lead loses 15-20 hours a week to coordination and you show two or three of the five signals, hire now. Don't wait for a headcount band. If there's an experienced engineer who wants the job and has the years behind them, promote and plan for a few months of ramp. If not, go external and budget the 60-90 days or more before they're effective.

If you're under about 8 engineers, or only one signal is flashing, add a senior or staff engineer first. If part of the team is contractors, assign someone in-house to own priorities and review before anything else. Whichever path you pick, write down the date you'll re-run the time log. The answer changes as the team grows.

Next step: if your team already blends employees and contractors, read how to run a team that mixes employees and contractors, since that's the day-to-day your first manager inherits.

Frequently asked questions

How many engineers before you need an engineering manager?

Sources range from 6-10 (open-source.io) to 8-14 (Algazzar) to 10-20 (Reinhard). All are heuristics. Use the band as a prompt to measure coordination load rather than as a trigger.

Is an engineering manager higher than a tech lead?

Not in a ranking sense. They're different tracks: the manager owns people and delivery, the tech lead owns technical direction. How a given company levels them is its own call.

What should an engineering manager do?

Hire, give feedback, grow people, keep delivery predictable, and clear what blocks the team. A first manager on a small team often also does some of the process work a CTO was covering. They shouldn't be the person making every architecture call.

How much does an engineering manager earn?

RecruitsLab's 2026 figures, in dollars, put base pay at $180K-230K for a first-time manager, $220K-280K at 3-5 years and $260K-340K at 5+ years. We found no trustworthy European figure, and pay varies by country, so check local data before setting a budget.

Should you promote your best engineer to manager?

Only if they want it, which is our advice, and have enough hands-on years behind them. Majors (2021) puts the bar at 5-7 years of hands-on engineering. Promoting the strongest coder by default often loses you a good engineer and gains an unhappy manager.

Do contractors need an engineering manager?

They need someone who owns their day-to-day work, but that person's job is delivery and integration rather than reviews and career growth. An in-house lead, tech lead or product owner can do it on a smaller team. As the contractor share grows, the load grows with it.