Platform engineering team archetypes
Three shapes we see working — and one common anti-pattern.
Across the platform engineering teams we hire for, three patterns consistently deliver. The first is the Product Platform team — small, opinionated, treats internal developers as customers, and ships paved roads with measurable adoption.
The second is the Embedded Enabler model. Platform engineers rotate into product teams for fixed engagements, transfer practices, and leave behind documentation. It works well in organisations with mature product engineering but uneven operational maturity.
The third is the SRE-Anchored team, where reliability engineering owns the platform surface and product teams self-serve via well-defined interfaces. This shape suits organisations with strict uptime requirements and a strong on-call culture.
The anti-pattern we see most often is the Rebranded Ops team — Ops engineers given the platform title without a product mandate, a roadmap, or the authority to deprecate legacy tooling. Adoption stays voluntary, internal customers route around them, and the team burns out maintaining bespoke pipelines.
If you're standing up a platform function, the org design matters more than the tooling choice. Pick the archetype that matches your engineering culture, then hire to it.