Span of Control in Engineering: When 7 Reports Is Too Many, When 4 Is Too Few

How many engineers can one manager support well? The question gets asked every reorg and almost never answered with a number. The empirical answer is a range — 5 to 8 for steady-state engineering management — but the more important answer is the set of variables that move that range. A manager of a senior, co-located, low-incident team can support 8 well; a manager of a junior, distributed, high-incident team should not be asked to support more than 4.

What span of control actually measures

Span of control is the number of direct reports a manager has. In engineering, the right number is whatever produces: weekly 1:1s with substantive content; quarterly career conversations; calibrated performance reviews; quality coverage during the manager's own vacation. If any of those drop, the span is too high regardless of the number.

The benchmark numbers

These numbers come from a synthesis of benchmarks: GitLab's published handbook, Google re:Work, Lara Hogan's writing, Camille Fournier's The Manager's Path, and the broader Conference of People in Engineering Leadership (CPiE) discussions. The convergence is striking — 5–8 is the dominant industry answer.

Variables that shrink the right span

• Distributed across 3+ timezones — shrink by 1–2.
• Junior-heavy team (>50% IC1–IC3) — shrink by 1–2.
• Manager is also acting as Tech Lead — shrink by 2–3 (or stop the dual role).
• Team owns a high-incident service (>2 pages/week) — shrink by 1.
• Heavy cross-team coordination load — shrink by 1.
• Recent reorg or new manager — shrink by 1–2 for 6 months.

Conversely, span can grow modestly when: team is senior and self-organising; manager is supported by a strong Tech Lead; the team owns a stable, low-incident product area; reports prefer minimal management overhead and have explicitly opted into less 1:1 time.

The math of 1:1 quality time

A working calculation makes the trade-offs concrete. Assume a manager has 30 hours per week of available time after meetings, email, and the basic operating overhead they cannot avoid.

By team type

When to split a team

1. Team consistently >9 engineers AND the manager is in coverage mode rather than coaching mode.
2. Two clear sub-domains have emerged inside the team's scope.
3. Stand-ups exceed 25 minutes regularly.
4. Cross-team coordination overhead is rising and meeting load is choking deep work.
5. A senior IC ready for first-line management has emerged.

Implications for HR

• Track manager span as a population metric. Anyone consistently above 8 should be a conversation, not an outlier.
• Don't reward span-as-status. 'I have 12 reports' should not be a promotion signal.
• Make first-time-manager span explicit in the onboarding plan.
• Watch for managers whose own 1:1 with their leader is repeatedly cancelled — they likely have no time left.
• When a team is in distress, span reduction is often the cheapest intervention available.

Anti-patterns

• Adding reports to a manager 'temporarily' during hiring freezes — temporary becomes permanent.
• Managers managing themselves (no manager above) — invisible failure mode at the senior layer.
• Span used as a proxy for level — converts a quality signal into a quantity contest.
• Skip-level meetings as a substitute for direct 1:1s when span is too wide.
• Span growth without an offsetting reduction in another responsibility.

Monday-morning checklist

• Pull current span for every EM and director. Flag anyone >8.
• Identify any first-time manager with >5 reports. Plan a reduction.
• Ensure every manager has a manager (no orphans at the senior layer).
• Add 'span of control' to your quarterly org review.
• Train recruiters that 'how many reports' is the wrong primary question in EM interviews.

FAQ

References