DEV Community

Cover image for The 10 most in-demand Cloud / DevOps roles

Posted on

The 10 most in-demand Cloud / DevOps roles

We thought it would be interesting to go deeper into the analytics part of running our DevOps job board – in the most privacy focused way for our users, of course. So here we are now starting to expose some of our aggregated internal job data in a systematic fashion through a simple REST API with a list of generalized job titles that are posted on

The cool thing with this is that we are able to see what’s popular in terms of the roles employers are hiring for most in the Cloud, Infrastructure and DevOps space.

Our “methodology” here is quite simple: we’re primarily counting the occurence of job titles over the last 12 months, cleaned and adjusted for certain specialties that some companies like to do, e.g. inventing their own stuff that’s not being used by anyone else or adding crazy super-specific details to a vacancy title and so on. We also left out many titles with indicators regarding seniority or other requirements as we already have dedicated attributes for these. More on that probably in a future post.

So here it is, our current (as of June 2021) top list of the ten Cloud / DevOps roles with the highest demand from employers on our site:

  1. DevOps Engineer
  2. Site Reliability Engineer
  3. Cloud Infrastructure Engineer
  4. Infrastructure Engineer
  5. Cloud Engineer
  6. QA Automation Engineer
  7. Cloud Architect
  8. DevSecOps Engineer
  9. Test Automation Engineer
  10. Platform Engineer

If your interested in the raw JSON data you can find the endpoint here:

The results there are updated every 6 hours, although it won’t really change that much anytime soon. And if it does we’ll probably write about it 😉

We also use all the job titles from that list for our brand new salaries survey to have a “standardized” selection of positions to choose from and attach salaries to. You can check out the survey – and the resulting dataset being released in the public domain – here:

This post was first published at

Top comments (0)