When platform work slows down, the instinct is to hire more platform engineers. I have rarely seen that fix anything. The teams that support hundreds of engineers with a handful of people all share the same shape: a thin platform group, golden-path defaults, and product teams that can self-serve without permission.
The thin platform team
Five to eight engineers is the sweet spot I keep seeing. Small enough to agree on standards, senior enough to build them once and properly. Their product is not clusters — it is the paved road: templates, pipelines, preview environments and the documentation that makes the road obvious.
- Platform owns the road, product teams own their services on it.
- Every manual ticket is a bug in the self-service offering.
- Headcount goes to golden paths before it goes to headcount.
Golden paths beat headcount
A service template that stamps out CI/CD, dashboards, alerts and cost labels in one pull request does the work of three hires. The supported way must also be the easiest way — the moment the easy path and the approved path diverge, engineers take the easy one and your standards become fiction.
When to actually hire
Hire when the paved road is crowded and the backlog is all new road — a second product surface, a new cloud, a compliance regime. Don't hire to staff a ticket queue; automate the queue and keep the team small enough to still agree over one whiteboard.
The best platform team is the one product engineers forget exists — until they need a new road, and it appears.
- Platform Engineering
- Team Topology
- DevOps
- Leadership
