Automation index
How much of a Security engineer’s job can AI already do?
A control comes earlier. Closing the hole without leaving the exception for ever do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Security engineer
27%
AI can already do 27% of this job.
#188 / 763
View rankingSecurity engineer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Control, the risk and the ticket.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Hole, the patch and the one still open.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Exception, the deadline and not leaving it for ever.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Identity, the privilege and not giving admin out of habit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The business, the rush and not opening the port 'for a moment'.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Close the hole, and not leaving the exception.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- security controls
- patches
- exceptions
- privileges
- ports
- identities
- not give admin
- holes
Sources for this job· O*NET 15-1212.00· ESCO/ISCO 2529
IS WORK OVER?
Front-end developer
27%
#154 / 763
View rankingFront-end developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513