Scaling Engineering: Ownership over Hiring
The article discusses how engineering organizations evolve as they grow, focusing on ownership structures and hiring practices at different team sizes (20, 50, and 200 engineers). It outlines key challenges and necessary changes in culture, communication, and management approach as a startup scales.
Background
- This post is by **Ido Green**, a long-time tech leader who worked at Google (on Chrome and Android) and helped scale developer platforms. His views carry weight because he's actually been inside big engineering orgs.
- The title refers to three common "scale thresholds" in tech: ~20 engineers (one team), ~50 (a small org or multiple teams), and ~200 (a full engineering division). Each stage breaks the old processes and forces new ones.
- The core argument is that **hiring fast without clear ownership** destroys culture. Many startups raise money and race to hire, but end up with "busy" people who don't own anything—leading to bugs, burnout, and no one accountable.
- The post contrasts two models: *ownership-driven scaling* (keep teams small, give each person clear domain responsibility, hire slowly) vs. *hire-first scaling* (fill seats, figure out roles later). The latter is the default in boom cycles and often fails.
- This ties into broader debates in the tech industry about **"engineering efficiency"** and whether more engineers actually ship more—a question companies from Meta to Stripe have publicly wrestled with in 2025-2026.