Which roles ask for Chaos Engineering at tech companies · 39 roles · 90 days to Nov 21, 2026
Updated
39 roles counted that list Chaos Engineering, one per company, title and level; 166 postings in the window.
This page opens in search once it reaches 50 roles in 90 days.
In short
Chaos Engineering: listed in 39 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 6 and preferred in 33. The largest group is site reliability engineer roles: 24 of 39.
- Required
- 6 of 39
- Of the roles that list Chaos Engineering
- Preferred
- 33 of 39
- Of the roles that list Chaos Engineering
- Largest group
- 24 of 39
- Site reliability engineer
Roles that ask for Chaos Engineering
Roles listing Chaos Engineering, by title family. Where the role has a page, the count is also out of that role's roles whose requirements we read.
| Role | Roles | Of the role's roles we read |
|---|---|---|
| Site reliability engineer | 24 | 24 of 351 |
| Software engineer | 7 | 7 of 4,983 |
| Platform engineer | 3 | 3 of 454 |
| QA engineer | 2 | 2 of 494 |
| Data scientist | 1 | 1 of 773 |
| DevOps engineer | 1 | 1 of 478 |
| Security engineer | 1 | 1 of 801 |
Companies that ask for it most
- Zscaler4 roles
- Cerebras Systems2 roles
- JumpCloud2 roles
- SecurityScorecard2 roles
- Circle1 role
- Cross River1 role
- Eclypsium1 role
- Ripple1 role
- Tango1 role
- Thrive Market1 role
Asked alongside
Out of the 39 Chaos Engineering roles whose requirements we read: the other skills they ask for. Too few to show shares, so we show counts.
| Skill | Roles asking |
|---|---|
| Python | 29 of 39 |
| Go | 25 of 39 |
| Observability | 25 of 39 |
| CI/CD | 22 of 39 |
| Kubernetes | 21 of 39 |
| Infrastructure as Code | 20 of 39 |
| Incident Response | 19 of 39 |
| Networking | 19 of 39 |
| Distributed Systems | 18 of 39 |
| Terraform | 17 of 39 |
| Skill | Roles asking |
|---|---|
| Terraform | 11 of 39 |
| Azure | 10 of 39 |
| AWS | 9 of 39 |
| Capacity Planning | 9 of 39 |
| Infrastructure as Code | 9 of 39 |
| Ansible | 7 of 39 |
| Observability | 7 of 39 |
| Argo CD | 6 of 39 |
| DNS | 6 of 39 |
| GCP | 6 of 39 |
Experience
Asked most often: 5–7 years, 14 of 35.
Of the 35 roles that state years
- Under 1 year
- 0 of 35
- 1 year
- 1 of 35
- 2 years
- 1 of 35
- 3–4 years
- 5 of 35
- 5–7 years
- 14 of 35
- 8–9 years
- 8 of 35
- 10+ years
- 6 of 35
Degree
5 of 39 require a degree, and 7 more accept experience instead.
Of the 39 roles we could read for it
- Required
- 5 of 39
- Required, or experience instead
- 7 of 39
- Preferred
- 3 of 39
- Not mentioned
- 24 of 39
Pay and remote work
Of the 39 roles we could read for it. Pay these roles state, not what the skill pays.
- Roles stating pay
- 20 of 39
- Remote roles
- 29 of 39
How we count: 39 roles from 33 employers in the 90 days to Nov 21, 2026, each role counted once however many boards post it. Skills are counted out of the roles whose requirements we read. Roles are not filtered by country. Methodology
Something wrong here?