What DevOps / SRE job postings ask for
Python appears in 76% of DevOps / SRE job postings — the term employers name most often.
Counted across 153 DevOps / SRE postings gathered from company career sites and seen in the last 90 days. Each percentage is the share of those postings naming the term at least once. Last verified ; re-checked every six hours.
Skills and tools, most-asked first
- Python76% 117 of 153
- Kubernetes68% 104 of 153
- Go56% 85 of 153
- Linux48% 73 of 153
- Terraform43% 66 of 153
- AWS35% 53 of 153
- Bash33% 51 of 153
- Azure26% 40 of 153
- Ansible25% 39 of 153
- Docker24% 36 of 153
- GCP22% 34 of 153
- Tcp/ip20% 30 of 153
- C++20% 30 of 153
- Bazel19% 29 of 153
- Java19% 29 of 153
- Prometheus18% 28 of 153
- Grafana18% 27 of 153
- CI/CD17% 26 of 153
- JavaScript16% 24 of 153
- Distributed systems10% 16 of 153
- AI10% 16 of 153
- Dns10% 16 of 153
- Puppet10% 15 of 153
- Makefiles9% 14 of 153
- Helm9% 14 of 153
Questions about this data
What skills do most DevOps / SRE job postings ask for?
Across 153 DevOps / SRE postings from the last 90 days, the most frequently named are Python (76%), Kubernetes (68%), Go (56%). Each percentage is the share of those postings naming the term at least once.
How common is Docker in DevOps / SRE postings?
Docker appears in 24% of the 153 DevOps / SRE postings counted — 36 of them exactly. That places it mid-pack rather than near-universal, which is worth knowing before you rewrite a résumé around it.
Where does this DevOps / SRE data come from?
Public job postings published by employers on their own career sites, collected through the official Greenhouse, Lever and Ashby job-board APIs. It is a count of 153 real postings seen in the last 90 days — not a survey, an estimate, or a model's guess.
Should I add these skills to my résumé?
Only the ones you genuinely have. Frequency tells you which terms to surface and phrase in the employer's own words if they are already true of you. Adding a skill you can't defend is the fastest way to fail an interview, so FreshStartr reports gaps rather than writing them in.
Other roles we track
Which of these does your résumé actually evidence?
Paste a DevOps / SRE posting and you get a line-by-line match report: what you already prove, and what you don’t. Gaps are reported, never written in for you.
Tailor your résumé to a DevOps / SRE posting