Platform engineering ate DevOps. The contract market noticed before the buyers did.

"DevOps engineer" as a job title peaked around 2022. Since then the European contract market has quietly re-labelled the top of the discipline as Platform Engineering — and the pay scale has followed the label.

What the title actually means now

A Platform Engineer in 2026 builds and owns the internal developer platform: golden paths, self-service infra, opinionated defaults, observability baked in. The scorecard is developer velocity and mean-time-to-production, not ticket throughput. The tooling clusters around Kubernetes, Terraform, Argo, Backstage and a growing set of internal CLIs.

The rate picture

Senior Platform Engineers band €780–1,020/day across the Nordics, Benelux and DACH. Staff Platform Engineers with a real IDP build story reach €1,050–1,300/day (AddanEx placements, Honeypot.io 2026). Traditional DevOps generalists with the same YOE now sit €150–250/day below.

Where buyers are getting it wrong

Two patterns. One: hiring a Platform Engineer to run pagers and rotate secrets — that's an SRE role wearing the wrong badge, and the person leaves inside six months. Two: hiring a senior DevOps generalist and expecting internal-platform outcomes. The disciplines have diverged; the contract market priced the split eighteen months ago.

The 2026 test

Before opening the search, write down the developer outcome you want to be different in twelve months. If it's "our teams ship in an afternoon instead of a fortnight", you're hiring a Platform Engineer. If it's "our alerts stop waking people up", you're hiring an SRE. If it's "our pipelines actually work", you're hiring a good DevOps engineer. Three different hires. Three different rate bands.