Which roles ask for Incident Response at tech companies · 960 roles · 90 days to Nov 21, 2026
Updated
960 roles counted that list Incident Response, one per company, title and level; 2,804 postings in the window.
In short
Incident Response: listed in 960 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 747 and preferred in 213. The largest group is security engineer roles: 269 of 960 (28%).
- Required
- 747 of 960 (78%)
- Of the roles that list Incident Response
- Preferred
- 213 of 960 (22%)
- Of the roles that list Incident Response
- Largest group
- 269 of 960 (28%)
- Security 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 |
|---|---|---|
| Security engineer | 269 | 269 of 801 (34%) |
| Software engineer | 243 | 243 of 4,983 (5%) |
| Site reliability engineer | 168 | 168 of 351 (48%) |
| Platform engineer | 104 | 104 of 454 (23%) |
| DevOps engineer | 75 | 75 of 478 (16%) |
| Data engineer | 40 | 40 of 867 (5%) |
| AI engineer | 12 | 12 of 507 (2%) |
| Forward deployed engineer | 11 | 11 of 340 (3%) |
| Software architect | 11 | 11 of 207 (5%) |
| Machine learning engineer | 10 | 10 of 538 (2%) |
Companies that ask for it most
Asked alongside
Out of the 960 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 | 528 of 960 (55%) |
| AWS | 449 of 960 (47%) |
| CI/CD | 395 of 960 (41%) |
| Kubernetes | 360 of 960 (38%) |
| Infrastructure as Code | 329 of 960 (34%) |
| Terraform | 319 of 960 (33%) |
| Go | 310 of 960 (32%) |
| Observability | 307 of 960 (32%) |
| Cybersecurity | 282 of 960 (29%) |
| Identity and Access Management | 276 of 960 (29%) |
| Skill | Roles asking |
|---|---|
| AWS | 107 of 960 (11%) |
| Kubernetes | 102 of 960 (11%) |
| Observability | 99 of 960 (10%) |
| CI/CD | 98 of 960 (10%) |
| AI | 92 of 960 (10%) |
| Terraform | 90 of 960 (9%) |
| Infrastructure as Code | 88 of 960 (9%) |
| SOC 2 | 81 of 960 (8%) |
| GCP | 73 of 960 (8%) |
| Python | 70 of 960 (7%) |
Experience
Asked most often: 5–7 years, 392 of 751 (52%).
Of the 751 roles that state years
- Under 1 year
- 0 of 751 (0%)
- 1 year
- 8 of 751 (1%)
- 2 years
- 41 of 751 (5%)
- 3–4 years
- 117 of 751 (16%)
- 5–7 years
- 392 of 751 (52%)
- 8–9 years
- 118 of 751 (16%)
- 10+ years
- 75 of 751 (10%)
Degree
72 of 955 (8%) require a degree, and 223 more accept experience instead.
Of the 955 roles we could read for it
- Required
- 72 of 955 (8%)
- Required, or experience instead
- 223 of 955 (23%)
- Preferred
- 55 of 955 (6%)
- Not mentioned
- 605 of 955 (63%)
Pay and remote work
Of the 960 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $180k a year
- Roles stating pay
- 475 of 960 (49%)
- Remote roles
- 691 of 960 (72%)
How we count: 960 roles from 693 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?