Which roles ask for Threat Modeling at tech companies · 281 roles · 90 days to Nov 21, 2026
Updated
281 roles counted that list Threat Modeling, one per company, title and level; 611 postings in the window.
In short
Threat Modeling: listed in 281 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 222 and preferred in 59. The largest group is security engineer roles: 210 of 281 (75%).
- Required
- 222 of 281 (79%)
- Of the roles that list Threat Modeling
- Preferred
- 59 of 281 (21%)
- Of the roles that list Threat Modeling
- Largest group
- 210 of 281 (75%)
- Security engineer
Roles that ask for Threat Modeling
Roles listing Threat Modeling, 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 | 210 | 210 of 801 (26%) |
| Software architect | 27 | 27 of 207 (13%) |
| Software engineer | 25 | 25 of 4,983 (1%) |
| DevOps engineer | 9 | 9 of 478 (2%) |
| Machine learning engineer | 3 | 3 of 538 (1%) |
| Site reliability engineer | 3 | 3 of 351 (1%) |
| AI engineer | 1 | 1 of 507 (0%) |
| Data scientist | 1 | 1 of 773 (0%) |
| Platform engineer | 1 | 1 of 454 (0%) |
| QA engineer | 1 | 1 of 494 (0%) |
Companies that ask for it most
- Anthropic3 roles
- Cohere3 roles
- Maven Clinic3 roles
- Offchain Labs3 roles
- OpenAI3 roles
- Field AI2 roles
- NVIDIA2 roles
- Nubank2 roles
- WHOOP2 roles
- Zscaler2 roles
Asked alongside
Out of the 281 Threat Modeling roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Python | 143 of 281 (51%) |
| AWS | 127 of 281 (45%) |
| Application Security | 125 of 281 (44%) |
| Cybersecurity | 108 of 281 (38%) |
| CI/CD | 105 of 281 (37%) |
| Go | 104 of 281 (37%) |
| Identity and Access Management | 94 of 281 (33%) |
| Kubernetes | 89 of 281 (32%) |
| Cloud Security | 84 of 281 (30%) |
| Vulnerability Management | 74 of 281 (26%) |
| Skill | Roles asking |
|---|---|
| AWS | 39 of 281 (14%) |
| SOC 2 | 38 of 281 (14%) |
| ISO 27001 | 35 of 281 (12%) |
| Incident Response | 29 of 281 (10%) |
| CI/CD | 27 of 281 (10%) |
| Penetration Testing | 27 of 281 (10%) |
| GCP | 26 of 281 (9%) |
| Kubernetes | 26 of 281 (9%) |
| Azure | 25 of 281 (9%) |
| Infrastructure as Code | 25 of 281 (9%) |
Experience
Asked most often: 5–7 years, 108 of 207 (52%).
Of the 207 roles that state years
- Under 1 year
- 3 of 207 (1%)
- 1 year
- 2 of 207 (1%)
- 2 years
- 7 of 207 (3%)
- 3–4 years
- 20 of 207 (10%)
- 5–7 years
- 108 of 207 (52%)
- 8–9 years
- 36 of 207 (17%)
- 10+ years
- 31 of 207 (15%)
Degree
16 of 280 (6%) require a degree, and 72 more accept experience instead.
Of the 280 roles we could read for it
- Required
- 16 of 280 (6%)
- Required, or experience instead
- 72 of 280 (26%)
- Preferred
- 19 of 280 (7%)
- Not mentioned
- 173 of 280 (62%)
Pay and remote work
Of the 281 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $192.5k a year
- Roles stating pay
- 148 of 281 (53%)
- Remote roles
- 189 of 281 (67%)
How we count: 281 roles from 241 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?