Which roles ask for Incident Response at tech companies · 167 roles · 90 days to Oct 7, 2026
Updated
167 roles counted that list Incident Response, one per company, title and level; 452 postings in the window.
In short
Incident Response: listed in 167 roles at tech companies whose requirements we read, in the 90 days to Oct 7, 2026. It was required in 118 and preferred in 49. The largest group is software engineer roles: 49 of 167 (29%).
- Required
- 118 of 167 (71%)
- Of the roles that list Incident Response
- Preferred
- 49 of 167 (29%)
- Of the roles that list Incident Response
- Largest group
- 49 of 167 (29%)
- Software engineer
Roles that ask for Incident Response
Roles listing Incident Response, 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 |
|---|---|---|
| Software engineer | 49 | 49 of 719 (7%) |
| Security engineer | 39 | 39 of 126 (31%) |
| Site reliability engineer | 39 | 39 of 70 (56%) |
| Platform engineer | 19 | 19 of 57 (33%) |
| Data engineer | 5 | 5 of 99 (5%) |
| DevOps engineer | 5 | 5 of 58 (9%) |
| Forward deployed engineer | 5 | 5 of 63 (8%) |
| AI engineer | 2 | 2 of 70 (3%) |
| QA engineer | 2 | 2 of 63 (3%) |
| Mobile engineer | 1 | 1 of 38 |
Companies that ask for it most
- GitLab9 roles
- Akamai Technologies5 roles
- CoreWeave5 roles
- Okta5 roles
- OpenAI4 roles
- Replit4 roles
- 1Password3 roles
- Databricks3 roles
- Stripe3 roles
- Zscaler3 roles
Asked alongside
Out of the 167 Incident Response roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Python | 93 of 167 (56%) |
| AWS | 76 of 167 (46%) |
| Go | 74 of 167 (44%) |
| Kubernetes | 69 of 167 (41%) |
| Observability | 68 of 167 (41%) |
| CI/CD | 59 of 167 (35%) |
| Infrastructure as Code | 57 of 167 (34%) |
| Terraform | 54 of 167 (32%) |
| Distributed Systems | 49 of 167 (29%) |
| GCP | 49 of 167 (29%) |
| Skill | Roles asking |
|---|---|
| CI/CD | 20 of 167 (12%) |
| Infrastructure as Code | 20 of 167 (12%) |
| Open Source | 20 of 167 (12%) |
| GCP | 18 of 167 (11%) |
| Kubernetes | 16 of 167 (10%) |
| AI | 15 of 167 (9%) |
| AWS | 15 of 167 (9%) |
| Terraform | 15 of 167 (9%) |
| Cybersecurity | 13 of 167 (8%) |
| Monitoring | 13 of 167 (8%) |
Experience
Of the 104 roles that state years
Each line counts roles asking for at least that many years, so the lines overlap.
- 1+ year
- 104 of 104 (100%)
- 2+ years
- 102 of 104 (98%)
- 3+ years
- 99 of 104 (95%)
- 5+ years
- 84 of 104 (81%)
- 8+ years
- 27 of 104 (26%)
- 10+ years
- 8 of 104 (8%)
Degree
Of the 141 roles we could read for it
- Required
- 3 of 141 (2%)
- Required, or experience instead
- 28 of 141 (20%)
- Preferred
- 4 of 141 (3%)
- Not mentioned
- 106 of 141 (75%)
Pay and remote work
Of the 167 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $196.3k a year
- Roles stating pay
- 83 of 167 (50%)
- Remote roles
- 94 of 167 (56%)
How we count: 167 roles from 104 employers in the 90 days to Oct 7, 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