Aggregated from live DevOps, SRE and platform engineering postings rather than opinion. Every figure below is measured from real adverts and recalculated daily.
A devops engineer builds the machinery that gets other people's code into production and keeps it there — the pipelines that test and ship every change, the infrastructure those changes run on, and the monitoring that says whether any of it is working. The point of all that automation is that deploying should stop being an event. The other half of the job is what happens when something breaks: being on call, finding the cause under time pressure, and then making that failure impossible rather than merely fixed. This page covers devops, SRE and platform engineering together, because employers use the three titles for substantially overlapping work.
Aggregated from the live descriptions of postings whose title names the role. Not a shortlist, and not anybody's opinion of what matters.
Share of DevOps Engineer postings mentioning the skill — a posting asks for many, so these do not add to 100. Measured across postings whose title is the role.
161 of those 2,150 remote DevOps Engineer roles are open to candidates anywhere in the world — the rest are remote within one country only. Most job boards do not separate the two.
The same skill list, split by the seniority of the posting asking for it. Bars run right where senior postings ask more often, left where mid-level postings do.
Percentage-point gap between the senior+ and mid-level shares naming each skill. Senior+ includes principal, staff and executive.
Everyone asks for the top of that first chart, so naming it proves nothing. These sit far enough down to differentiate you, and close enough to the top to be worth the effort.
United States 2,029 
Singapore 297 
India 240 
United Kingdom 154 
Germany 132 
Netherlands 111 
Thailand 93 
Canada 88 Where our listings sit, not the world's — the corpus skews to US and English-language boards.
· United States
· India
· United States
· Canada
· Singapore
· United States
· Malta
· Malta
· Malta
· Ireland
· United States
· Israel
· Denmark
· India
· Germany
· United States
· Canada
· United States
· United States
· United Kingdom
· Canada
Free. No card required. Every role ranked against your CV.
Compare the top of this chart with the equivalent on the backend or data pages and the difference is obvious: those roles spread across many valid choices, while this one converges hard on a small set of tools. Containers, orchestration, infrastructure as code, a pipeline runner and a cloud platform account for a large share of everything asked for.
That convergence cuts both ways. It makes the role unusually learnable — the list of things to know is short and public — and unusually competitive, because everyone applying has learned the same list. Which is what makes the rarer skills further down this page worth more here than almost anywhere else on the site.
The seniority split on this page is a useful read for anyone trying to move up. What separates senior postings is rarely another tool; it is the language of scale, reliability and designing systems other engineers depend on.
That is hard to demonstrate from a course and straightforward to demonstrate from having run something. If you have carried a pager for a system with real users, that is the experience these postings are actually asking about.
Containers and orchestration, infrastructure as code, CI/CD pipelines, at least one major cloud platform, and enough scripting to glue them together — plus monitoring and observability. The ranked list above gives the current share of postings naming each, recalculated daily.
The chart above shows the split, read as minimums. DevOps skews later than most technical roles: entry-level postings are a small share, largely because the work is about operating systems under failure and that is difficult to evidence without having done it.
It is one of the more natural moves, because the overlap in tooling is large and the pipeline and infrastructure work is already adjacent to what most engineers touch. The gap tends to be operational rather than technical — being responsible for what happens at 3am is a genuinely different job.
The work-policy chart above shows the actual split for these postings, along with the number open to candidates in any country rather than remote within one. On-call requirements sometimes come with time-zone expectations that a "remote" label does not capture, so the description is worth reading.
Less than the titles suggest, which is why this page covers them together. Broadly: devops describes the practice of shortening the path from code to production, SRE applies engineering discipline to keeping a specific system reliable, and platform engineering builds internal tooling for other engineering teams. Many postings use the terms interchangeably.
Upload your CV once. Every role here gets scored 0–100 against it, so you apply to the ones where you have a real shot.
Free to start · no card required
Malta 
Ireland 
Israel 
Denmark