When to Hire Your First Engineering Manager

Hire your first engineering manager when your team grows past about 10 engineers, or earlier if you can no longer hold regular one-to-ones, unblock work and still ship your own. Bessemer Venture Partners' scaling guide says that beyond 10 engineers you should bring in at least one manager. Everything else on the signals list below is our rule of thumb, not research.

This guide covers the signals that it is time, whether to promote or hire, what the first manager should own, how to run the interview loop and what your job becomes afterwards. It extends the breakpoints in scaling an engineering org, and the free engineering org chart tool shows what a suggested structure looks like at your headcount. Sourced thresholds are labelled; practitioner judgement is labelled too.

What headcount means it is time for a first engineering manager?

Bessemer's Atlas guide describes three early stages. From seed to about 10 engineers, the leader should be hands-on in the code. Beyond 10, add at least one manager to prioritise projects, manage workloads, address issues and set minimum processes. Around 20, decide whether the current CTO can lead the next stage. Career paths and performance plans, it says, can wait.

Source: Bessemer Venture Partners Atlas, Scaling your engineering team from one to 50 and beyond. The guide gives no ratio of engineers to managers and does not cover whether to promote or hire; treat the rest of this article as practitioner guidance.

Headcount is a proxy. Two companies with 12 engineers can need different things: a team of twelve senior engineers on one product can run with a lighter hand than twelve mixed-seniority engineers across two products. Use the headcount rule as the trigger to look, then use the signals below to decide.

What are the signals that you need an engineering manager?

The strongest signal is that you are the bottleneck: decisions, reviews and unblocking wait for you, and your one-to-ones keep slipping. The table lists the signals we see most often, with the basis for each, so you can separate sourced guidance from judgement.

Check your reading with data where you can. DORA's guidance applies delivery metrics per team; falling throughput or rising change failure on a growing team is a prompt to look at coordination, not proof that you need a manager. See engineering metrics for CTOs for how to read them without over-interpreting.

One warning from the research on managers generally: Gallup's 2024 State of the Global Workplace reports that manager engagement fell from 30% to 27%, the sharpest decline of any group, and that managers given best-practice training saw their teams' engagement improve substantially (Gallup). It is a global, all-industry survey, not an engineering one, but it supports a point that matters here: a first-time manager needs training and support, not just a title.

Should you promote an engineer or hire an engineering manager?

Promote when you have a senior engineer who already coaches others and wants the job. Hire when no one is ready or wants it, or when you need someone who has managed before. Neither option is safer; each fails in a predictable way. The table is our editorial comparison. No published study we found compares the two routes for a first engineering manager.

Whichever route you choose, say plainly in advance that management is a different job, not a promotion. Offer a path back for a promoted engineer. Many first-time managers discover they prefer the individual-contributor track, and the company should not penalise them for finding out. If you are weighing the change yourself, see engineering manager to CTO, which describes what engineering managers already bring and where the gaps are.

What should the first engineering manager own?

The first engineering manager should own people and delivery for one team, not the architecture and not the whole org. Bessemer's description of the role is deliberately modest: set priorities, manage workloads, address issues and put minimum processes in place. Our recommended split below keeps the CTO accountable for strategy and gives the manager clear authority where it matters.

Write this down. Ambiguity about decision rights is the most common reason a new manager and a CTO fall out. Agree which decisions the manager makes alone, which they make after consulting you, and which are yours. A one-page agreement reviewed monthly is enough. Tell the CEO as well, because a new layer changes how engineering updates reach them.

Bessemer also advises bringing in outside expertise for consequential decisions such as data stores or whether to build a separate quality team. Do not ask your first manager to decide these alone; the manager's job is to run the team that implements them.

How should you interview an engineering manager?

Run a loop that tests people skills, delivery judgement and technical credibility, in that order of weight. A first engineering manager at a small company should be credible with engineers without trying to out-code them. The stages below are our suggested loop, not a published standard.

1. Conversation with you (45 to 60 minutes). Cover their management history, why they want the role and how they handle disagreement with a boss. Ask what they would do in the first 30 days.
2. Situational round on people issues. Use scenarios: an underperforming senior engineer, a conflict between two engineers, a team member asking for promotion. Look for specific past examples and for how they involved the person.
3. Delivery and planning round. Give a realistic project with an unclear scope and a slipping date. Ask them to walk through how they would plan, communicate and re-scope.
4. Technical conversation, not a coding test. Check that they can discuss design trade-offs, review code and understand incident causes. The aim is credibility with the team.
5. Meet the team. Have two or three engineers talk to the candidate and give you structured feedback.
6. References. Speak to people they managed, not only their managers.

For interview craft from the candidate side, which helps you read what a good answer sounds like, see CTO interview questions.

What is your job after the hire?

Your job changes from deciding to developing the manager. Delegate decisions explicitly, resist stepping back in when the manager chooses differently from you, and meet weekly in the first months. The common failure is a CTO who hires a manager and then keeps doing the manager's job.

A practical sequence for the first quarter, as editorial guidance:

• Weeks 1 to 2. Introduce the manager to the team yourself, hand over one-to-ones gradually and share the context on each person.
• Weeks 3 to 6. Let the manager run planning and retrospectives. Attend only as an observer.
• By week 8. Review the decision-rights agreement and what is working. Adjust.
• By week 12. Gather feedback from the team and set the manager's first quarterly goals.

Invest in the manager's development. Training programs exist for new managers; our best engineering manager courses guide compares options with checked prices. Plan the next step too: Bessemer's decision point around 20 engineers is when you choose whether to grow into the people-and-scaling role yourself or add a VP or SVP of Engineering (Bessemer Atlas). See CTO vs VP of Engineering.

What mistakes should you avoid?

Four mistakes recur. First, hiring too early, before there is enough work to manage, which leaves the manager either coding or inventing process. Second, hiring too late, after engineers have already left. Third, promoting the best engineer because they are the best engineer, rather than because they want the job. Fourth, giving the title without the authority, so every decision still waits for you.

Frequently asked questions

When should a startup hire its first engineering manager?

Bessemer Venture Partners' guidance is to add at least one manager once the team grows beyond about 10 engineers, with a hands-on leader before then. The other signals are our rule of thumb: one-to-one debt, you being the bottleneck, and missed delivery with no clear owner. Use headcount as the trigger to look, not the only test.

Should I promote a senior engineer or hire an engineering manager?

Promote if a senior engineer already mentors others and genuinely wants to manage; hire if no one is ready or you need someone who has managed before. Whichever you choose, offer a way back to the individual-contributor track and provide management training. No published study compares the two routes, so this is practitioner judgement.

What should a first engineering manager do?

Own people and delivery for one team: one-to-ones, planning, prioritisation, basic process and early risk reporting. The CTO keeps architecture, cross-team priorities and escalations. Write down which decisions the manager makes alone, which require consulting you and which stay with you, and review the agreement monthly.

How many engineers should report to an engineering manager?

No authoritative ratio exists. Bessemer's guide gives none. As a rule of thumb, which is practitioner judgement rather than research, teams often use roughly five to eight direct reports per manager and adjust for seniority and how hands-on the manager is. Our org chart tool uses the same heuristic.

Does a first engineering manager still write code?

Rarely, and it depends on team size. Bessemer says a leader should be hands-on in the code up to about 10 engineers, but a manager hired beyond that point is there to set priorities, balance workloads and address issues. Keep their coding small and non-critical, so work is never blocked on them.

Sources

1. Scaling your engineering team from one to 50 and beyond Bessemer Venture Partners (Atlas), 2026
2. State of the Global Workplace Gallup, 2024
3. DORA metrics: the four keys (current five-metric model) DORA, 2026

How we source and check figures: Methodology.