A surprising number of “platform engineering” job adverts are, on inspection, DevOps roles with a more fashionable title. The two practices share tools and personnel, but they answer different questions. DevOps is concerned with how software gets safely into production. Platform engineering is concerned with the experience of the developers who build that software.
The distinction matters because it changes what good looks like. A DevOps team optimises for deployment frequency, change failure rate, recovery time. A platform team optimises for time-to-first-pull-request, cognitive load, and the rate at which developers stop opening tickets and start self-serving. The metrics overlap but they aren’t the same.
When organisations conflate the two, they tend to staff platform teams with their best operations engineers and then wonder why developer experience is still poor. Operations engineers build robust systems. Platform engineers build robust systems that are also pleasant to use, and the second skill is rarer.
If your platform team’s roadmap is indistinguishable from a list of infrastructure upgrades, you have a DevOps team with a new logo.
Alex
