Blog post

Platform Engineer vs SRE vs DevOps: Overlapping Work, a $50,000 Pay Gap

4 min read
Share:

Table of Contents

Show

Say you keep production running for a living. Depending on the company, your title is platform engineer, site reliability engineer, DevOps engineer or infrastructure engineer, and the work overlaps a lot. The titles do not pay the same, though, and they are not hiring at the same pace.

We counted on October 6, 2026, across the tech companies we track, as distinct roles (one role posted in ten cities counts once):

Title familyOpen rolesCompaniesMedian pay midpointRoles with pay
Platform engineer164104$210,00081
Infrastructure engineer10069$202,50052
Site reliability (SRE)17593$186,50089
DevOps10580$160,00030

(A few roles carry two of these titles at once, so the rows overlap slightly.)

Same family of work, a $50,000 spread between the top and bottom title. The DevOps figure rests on only 30 roles with published pay, so hold it loosely. DevOps also lost the most ground in the next table.

All four are losing share, DevOps fastest

Among companies we have tracked since before mid-May, here is each title's share of the roles opened in two windows:

Title familyEarly June to early AugustSince early September
Platform1.16%1.00%
SRE1.26%1.20%
DevOps0.96%0.74%
Infrastructure0.56%0.48%

Every one of them dipped, and DevOps fell the most, about a quarter of its share in a few months. These are small numbers (26 to 132 roles per window), so we would not read too much into the exact sizes. But the title that pays least is also shrinking fastest.

We do not think the work is going away. Kubernetes, Terraform and cloud skills show up all over the board, inside backend, security and AI roles. What may be fading is the separate DevOps job title, as that work moves into platform teams or into every engineer's job.

The same stack, mostly

Title familyTop of the stack
PlatformPython, Kubernetes, AWS, Terraform, Go
SREKubernetes, Python, AWS, Go, Terraform, Prometheus
DevOpsKubernetes, Terraform, AWS, Python, Docker, Ansible
InfrastructureKubernetes, Python, AWS, Terraform, Go, Rust

The differences are small but telling. Go shows up near the top for platform, SRE and infrastructure roles and not in the DevOps top ten. Ansible makes the DevOps and infrastructure top tens but not platform or SRE. Rust makes the infrastructure top ten. Our reading: the better-paid titles ask you to write more software, not just configure it.

Who hires each

Seniority and remote

All four lean senior, and juniors are rare everywhere: 1 junior platform role, 2 SRE, 2 DevOps, 3 infrastructure. SRE has the most roles labelled remote from anywhere (13). The others have four or five each. Remote within a country or region is the most common setup for all four.

If this is your work

  1. Title yourself for the job you want. Similar skills are listed under "platform" for more money than under "DevOps".

  2. Write code. Go (and sometimes Rust) shows up more in the stacks of the higher-paid titles.

  3. Search all four titles. They overlap so much that limiting yourself to one leaves out roughly two thirds of the openings.

You can search all four on our tech job board by title or by stack, and an agent can search the board without an account.

Caveats

Pay is the median of each band's midpoint, normalized to US dollars a year, and only for roles that publish one. Title matching is a pattern, so some roles land in two families and some infrastructure work hides under plain "Software Engineer" titles. The trend windows count roles at companies we tracked through both. All of it is October 6, 2026.

If you hold one of these titles and think we have the pay order wrong, tell us in Discord.

Find your next role

Browse hundreds of tech companies by stack. Let your AI agent handle the search. Free to start.