How Many Direct Reports Should an Engineering Manager Have?

The research says 5-9. Reality is messier.

Every engineering manager eventually asks this question: how many people should I actually manage?

The answer matters more than most people think. Too few reports and you're a glorified tech lead. Too many and you're a meeting machine who can't give anyone meaningful attention.

What the Research Says

The most-cited number comes from management research going back decades: 7 ± 2 direct reports is the sweet spot.

Here's why that range exists:

• 
  Below 5 reports: You're probably not fully utilized as a manager. Companies will either add IC work to your plate (making you a player-coach, which has its own problems) or question whether the role needs to exist.


• 
  5-7 reports: The goldilocks zone. Enough people to justify a full-time management role, few enough that you can have meaningful weekly 1:1s, give real feedback, and actually know what each person is working on.


• 
  8-9 reports: Manageable if your team is senior and autonomous. You'll need to be disciplined about where you spend your time.


• 
  10+ reports: You're in survival mode. 1:1s become biweekly or superficial. You miss signals — burnout, disengagement, blockers that fester.

The Variables Nobody Talks About

That 7±2 number assumes a lot. In practice, your capacity depends on:

Team seniority

A team of senior engineers who are self-directed and experienced needs less management overhead than a team with multiple junior developers who need mentoring, code review guidance, and career coaching.

How much IC work you're doing

If you're still writing code 40% of the time (common at startups), you effectively have half the management capacity. A player-coach managing 7 people is really managing 7 people with 3 people's worth of attention.

Organizational complexity

Cross-team dependencies, stakeholder management, hiring — these all eat into your people-management bandwidth. If you're spending 30% of your week in cross-functional meetings, your effective span of control shrinks.

Whether your team has an EM or tech lead split

Some orgs split people management (EM) from technical leadership (tech lead or staff engineer). If you have a strong tech lead handling architecture decisions and technical mentoring, you can manage more people.

What Actually Happens at Scale

Here's what I've observed at companies of different sizes:

• 
  Startups (< 50 eng): Managers often have 4-6 reports but are also player-coaches. Effective span is more like 3-4.


• 
  Growth stage (50-200 eng): This is where span problems hit hardest. Rapid hiring means managers suddenly go from 5 to 10+ reports. This is the #1 cause of manager burnout I've seen.


• 
  Enterprise (200+ eng): Usually better about maintaining 5-8 report ratios, but org complexity adds hidden overhead.

The Real Question: Can You Give Each Person What They Need?

Instead of obsessing over a number, ask yourself:

1. 
   Can I have a meaningful 1:1 with each report every week? Not a status update — a real conversation about their work, growth, and blockers.


2. 
   Would I notice if someone was burning out? If you don't have enough signal from your team to catch this early, you have too many reports.


3. 
   Can I write a thoughtful performance review for each person? If you're copy-pasting generic feedback, you're spread too thin.


4. 
   Do I know what each person wants to do next in their career? Not their job title aspiration — their actual growth areas and interests.

If you answered "no" to any of these, you either have too many reports or you need better systems to stay informed.

Building Systems That Scale

The managers I've seen handle larger teams well all have one thing in common: they build systems instead of relying on memory and heroics.

A few that help:

• 
  Async standups instead of daily meetings. You get signal without burning calendar time. Tools like Vereda run these in Slack and use AI to surface patterns — blockers that keep recurring, people who seem stuck, workload imbalances.


• 
  Structured 1:1 docs that carry forward context week to week. If you're starting every 1:1 with "so what's going on?" you're wasting the first 10 minutes rebuilding context.


• 
  Lightweight team health metrics. Not surveillance — just enough signal to know where to focus your attention. Are standups getting shorter (possible disengagement)? Is one person always blocked on the same dependency?

The Bottom Line

5-7 is the sweet spot for most engineering managers. Go above 9 and you're making tradeoffs you probably shouldn't. Go below 4 and make sure you're adding enough value to justify a dedicated management role.

But the number is less important than the quality of attention you give each person. A great manager with 8 reports and good systems will outperform a mediocre manager with 5.

I'm building Vereda — a free Slack standup bot with AI analytics for engineering teams. It helps managers stay informed without adding meetings, especially as teams grow. If managing a growing team is something you're dealing with, check it out.