Security Guard vs Software Engineer: which is more exposed to AI?
32 points apart. These are not comparable risk profiles.
Software Engineer sits at 67% time-weighted AI exposure against 35% for Security Guard, a 32-point gap driven by the 32% of software engineer work time that current models can already substitute outright. Security Guard holds a larger human-critical core — 46% of the role's time sits in work like "de-escalate confrontations" that models score poorly on. The two sit in different families — Protective Services and Computer & Math — so any move between them is a career change, not a lateral step.
Seven dimensions, side by side.
What actually creates the gap.
Both roles hand a similar slice of the week to substitutable work — 30% for Security Guards, 32% for Software Engineers — but it is different work. Security Guard exposure concentrates in "write incident reports"; Software Engineer exposure concentrates in "write boilerplate & crud code". Two roles can share a score and face completely different disruption timelines.
- Write incident reports82% · 8% time
- Log visitor entries78% · 6% time
- Draft shift handoffs76% · 4% time
- Monitor camera feeds74% · 12% time
- De-escalate confrontations8% · 8% time
- Respond to incidents on site10% · 12% time
- Support emergency evacuations12% · 4% 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 procedural — that is the part of your experience that travels intact. The real divide is manual: Security Guards score 74 there against 6 for Software Engineers, a 68-point spread. That is the gap you would actually have to close.
| DIMENSION | SECURITY GUARD | SOFTWARE ENGINEER |
|---|---|---|
| Manual | 74 | 6 |
| Creative | 6 | 61 |
| Cognitive | 24 | 78 |
Neither role lists the other as a mapped adjacent career, and the capability profiles sit 44 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.
Score your own exposure in 8 questions →Common questions.
Is Security Guard or Software Engineer more at risk from AI?
Software Engineer. It scores 67% time-weighted AI exposure against 35% for Security Guard — a 32-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 30% for Security Guards.
Which pays more, Security Guard or Software Engineer?
Software Engineer, by roughly $95k at the median ($132k versus $37k). 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 guard switch to being a software engineer?
Neither role lists the other as a mapped adjacent career, and the capability profiles sit 44 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.
Which role is growing faster, Security Guard or Software Engineer?
Software Engineer, at 17% projected ten-year growth versus 2% — a 15-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.