Founders and tech leads often run engineering for a long time before bringing in a dedicated manager. Waiting too long burns you out and caps team growth; hiring too early adds overhead and can feel like losing control. Here’s how to decide when to hire your first engineering manager and how to make the transition work.
Signs It’s Time
You’re the bottleneck.
Every hire, every priority call, and every conflict flows through you. You don’t have time for strategy or product because you’re always in the weeds. The team could be bigger and more effective if someone else owned people and process.
The team has reached a size where 1:1s and context don’t scale.
Rough rule of thumb: once you’re past about six to eight direct reports, quality of 1:1s and clarity of expectations drop. People don’t get enough of your time, and you can’t keep everyone’s context in your head.
You’re not the right person for the people work.
You might be a strong technical leader but dislike or struggle with performance conversations, career development, and conflict. The team would be better served by someone who cares about and is good at that.
You need to focus elsewhere.
Your highest leverage might be product, company strategy, or architecture. If managing the team is crowding that out, delegating management frees you for what only you can do.
None of these is a strict rule. The real test: “Would the team and I be better off if someone else owned management so I could do X?”
What the First Engineering Manager Should Be
- Comfortable with people and process. 1:1s, feedback, hiring, and conflict don’t scare them. They don’t have to have been a manager for years, but they should want to do the job and have some evidence (e.g. mentoring, leading projects).
- Aligned with you on direction. They don’t need to make every technical call, but they need to understand and support where the product and the team are going. You’ll work closely at first.
- Able to earn the team’s respect. The team needs to see them as credible—through past experience, judgment, or how they handle the first few months. Someone who’s only “good at HR” and not technical enough may struggle.
- Willing to own the hard stuff. Performance issues, saying no, and representing the team to the rest of the company are part of the role. You need someone who will take that on, not escalate everything to you.
Internal promotions can work if someone has the inclination and you’re ready to support them. External hires can bring experience and a fresh view. Choose based on who’s available and what the team needs most.
How to Make the Transition Work
Define the handoff.
What are they responsible for on day one? Typically: 1:1s, performance and development, hiring (with you for a while), and team process (standups, planning, retros). What stays with you? Strategy, key stakeholder relationships, and maybe final say on architecture or hiring until they’re up to speed. Write it down and share it with the team.
Introduce them clearly.
“X is now your manager for growth, feedback, and how we work. I’m still involved in [product/tech direction], but your 1:1s and day-to-day support are with X.” Avoid “we’re co-managing” unless you’ve really defined what that means; otherwise the team won’t know who to go to.
Step back in the right places.
Don’t keep doing 1:1s or resolving every conflict. Let the new manager own it. Your job is to support them (advice, context, backup) and to hold them accountable for outcomes, not to do their job.
Check in with the team and with them.
In the first few months, ask the team how it’s going and ask the manager what’s hard. Adjust the split of responsibilities as you learn. If you under-delegate, they’ll feel like a “lead” with a title; if you over-delegate without support, they’ll struggle.
What to Avoid
- Hiring a “mini you.” You need someone who complements you and can own management, not a clone.
- Keeping all the “interesting” work. If you keep all the key decisions and relationships, the manager role feels empty. They need real scope and visibility.
- Expecting instant change. It takes time for the team and the new manager to build trust and rhythm. Give them a few months before judging.
When to hire your first engineering manager comes down to: you’re the bottleneck, the team size or needs exceed what you can do well, and you have (or can find) someone who can own people and process. Plan the handoff clearly, step back where they own the work, and support them so the transition actually frees you and grows the team.