Security Engineer vs Software Engineer: which is more exposed to AI?
A 27-point gap separates these roles — Security Engineer is the more defensible seat.
Software Engineer sits at 67% time-weighted AI exposure against 40% for Security Engineer, a 27-point gap driven by the 32% of software engineer work time that current models can already substitute outright. Security Engineer holds a larger human-critical core — 47% of the role's time sits in work like "advise leadership on risk acceptance" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.
Seven dimensions, side by side.
What actually creates the gap.
Software Engineers spend 32% of their time-weighted week on tasks a current model can produce end-to-end, against 19% for Security Engineers. The single largest contributor is "write boilerplate & crud code", graded at 92% and worth 14% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.
- Generate security reports82% · 5% time
- Run automated vulnerability scans78% · 6% time
- Draft security policies74% · 4% time
- Summarize threat intelligence72% · 4% time
- Advise leadership on risk acceptance12% · 8% time
- Respond to active intrusions15% · 16% time
- Lead red-team exercises20% · 9% time
- Write boilerplate & CRUD code92% · 14% time
- Generate unit tests from specs88% · 8% time
- Author documentation85% · 6% time
- Translate code between languages81% · 4% time
- Mentor junior engineers11% · 3% time
- Negotiate scope with stakeholders14% · 5% time
- Triage production incidents22% · 4% time
Both roles lean on cognitive, procedural — that is the part of your experience that travels intact. The real divide is judgement: Security Engineers score 80 there against 41 for Software Engineers, a 39-point spread. That is the gap you would actually have to close.
| DIMENSION | SECURITY ENGINEER | SOFTWARE ENGINEER |
|---|---|---|
| Judgement | 80 | 41 |
| Creative | 44 | 61 |
Software Engineer appears in our dataset as a mapped adjacent career for Security Engineers: the move raises exposure by 27 points, landing at 67%. Switch difficulty reads low — capability profiles are 19 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is Security Engineer or Software Engineer more at risk from AI?
Software Engineer. It scores 67% time-weighted AI exposure against 40% for Security Engineer — a 27-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 19% for Security Engineers.
Which pays more, Security Engineer or Software Engineer?
Software Engineer, by roughly $7k at the median ($132k versus $125k). Note that the higher-paying role here is also the more AI-exposed one, which matters if you are weighing pay against durability.
Can a security engineer switch to being a software engineer?
Software Engineer appears in our dataset as a mapped adjacent career for Security Engineers: the move raises exposure by 27 points, landing at 67%. Switch difficulty reads low — capability profiles are 19 points apart on average and both sit in the same family.
Which role is growing faster, Security Engineer or Software Engineer?
Security Engineer, at 30% projected ten-year growth versus 17% — a 13-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.