Scaling engineering teams without breaking culture
Growing a team from 5 to 30 is a fundamentally different challenge than growing from 30 to 80. Here's what I've learned from doing both.
Growing a team from 5 to 30 is a fundamentally different challenge than growing from 30 to 80. The instincts that work at one scale actively break things at the next.
The 5-to-30 transition
At this stage, most of the friction comes from informal processes that worked fine when everyone sat together but collapse under headcount. Decisions that used to happen over lunch now need a meeting. Context that lived in one person's head needs to be written down.
The most important things to get right at this stage:
- A clear engineering career ladder so people know what growth looks like
- Lightweight architecture decision records (ADRs) so new joiners understand why things are the way they are
- A consistent onboarding process — even a simple checklist beats nothing
The 30-to-80 transition
By the time you hit 30 engineers, you probably have teams within the team. The challenge shifts from process to alignment. You're no longer worried about whether decisions get made — you're worried about whether the right decisions get made, and whether people across different pods are rowing in the same direction.
This is where engineering leadership becomes less about technical judgment and more about communication, trust, and org design.
The details change with every company, but the underlying pattern is consistent: what got you here won't get you there. Recognising the transition early — and deliberately designing for the next stage rather than patching the current one — is the difference between scaling and surviving.