Engineering Manager to IC Ratio
Why 5-8 Works
The 5-8 range isn't arbitrary. It comes from practical time constraints. A good engineering manager spends 30-45 minutes per week in 1:1s with each report, plus time on career development planning, performance reviews, hiring, cross-team coordination, and process improvement. With 5 reports, that adds up to roughly 15-20 hours per week on people management. With 8 reports, it's closer to 25-30 hours. At 10+, something has to give, and it's usually the quality of 1:1s and career conversations.
The research backs this up. Studies from Gallup and the Corporate Leadership Council consistently show that manager effectiveness drops sharply above 8 direct reports, with employee engagement scores declining in lockstep.
When Ratios Should Shift
Not every team is the same. Factors that push the ratio lower (toward 5):
- New teams that are still forming and need heavy coaching
- Junior-heavy teams where engineers need more mentorship and direction
- High-complexity domains like infrastructure, ML, or security where technical decisions carry outsized risk
- Teams in crisis dealing with reliability problems, attrition, or major refactors
Factors that allow a higher ratio (toward 8-9):
- Senior-heavy teams with experienced ICs who are largely self-directed
- Stable products in maintenance mode with well-understood requirements
- Strong tech leads who handle day-to-day technical leadership, freeing the manager to focus on people
The Manager-of-Managers Transition
This is one of the hardest transitions in engineering leadership. A manager-of-managers (typically a Director) stops managing individual engineers and starts managing other managers. The skills shift dramatically: from career coaching ICs to developing managers, from making technical decisions to setting technical direction, from team-level planning to org-level strategy.
Most companies need this role around the 40-60 engineer mark, when you have 5-8 teams and the VP of Engineering can no longer maintain direct relationships with all managers.
Skip-Level 1:1s
Every director and VP should run skip-level 1:1s with ICs in their org. These aren't performance reviews or an end-run around the manager. They're a feedback channel. Ask questions like "What's the biggest thing slowing your team down?" and "Is there anything you think leadership should know about?" Monthly or quarterly cadence works. More frequent than that starts to undermine the direct manager relationship.
Key Points
- •The sweet spot for most engineering managers is 5-8 direct reports. Below 5, the manager lacks enough context to justify the role. Above 8, 1:1s and career development conversations get squeezed and people start feeling invisible
- •Span of control should decrease as team complexity increases. A manager overseeing a mature CRUD service team can handle 8 reports. A manager overseeing a team building distributed systems from scratch should have closer to 5
- •Skip-level 1:1s (a manager's manager meeting directly with ICs) are essential for catching blind spots. Run them monthly or quarterly. They surface problems that people won't raise with their direct manager
- •The player-coach model (manager who also writes production code) works briefly during transitions but fails as a permanent structure. Either the management work suffers or the engineering work suffers. Usually both
- •Adding a management layer is a one-way door that's hard to undo. Only add a manager-of-managers role when you have 3+ managers, each with 5+ reports, who need coordination and career development that the director can't provide alone
Common Mistakes
- ✗Promoting the best engineer to manager without training or a trial period. Technical excellence and people management are orthogonal skills. Offer management rotations or tech lead roles as a bridge
- ✗Keeping span of control too narrow because managers want to stay close to the code. If a manager has 3 reports and spends 60% of their time coding, you've created an expensive tech lead, not a manager
- ✗Ignoring the transition pain when an IC's manager changes. Relationship continuity matters for career development. When you restructure, give people advance notice and let them have input on where they land
- ✗Assuming flat structures scale. Companies like Valve and GitHub tried minimal management and eventually added layers because coordination costs grew faster than headcount