The Art of CTO Engineering Org Designer models team structures, reporting lines, and organizational patterns to help CTOs plan engineering department growth and reorganization.
Frequently Asked Questions
How should you structure an engineering organization?
Engineering org structure depends on company size and product complexity. Small teams (under 20) typically use a flat structure with a single engineering manager. Mid-size teams (20-80) benefit from a two-level structure organized around product areas or domains, with engineering managers reporting to a VP or CTO. Large organizations (80+) need a three-level structure with directors overseeing multiple teams. The key principle is aligning team boundaries with system architecture (Conway's Law) so each team can own and ship independently.
What is the right ratio of managers to ICs in engineering?
The optimal ratio varies by team maturity and domain complexity. For most engineering organizations, aim for 6-8 ICs per engineering manager. Senior, autonomous teams can stretch to 8-10. Teams with many junior engineers or complex cross-team coordination needs should stay at 5-6. Beyond direct reports, consider the total management overhead: directors should manage 4-6 engineering managers, and VPs should manage 3-5 directors. Exceeding these ratios typically results in insufficient coaching, delayed feedback, and missed growth opportunities for reports.