Automation index
How much of a Requirements engineer’s job can AI already do?
A backlog comes earlier. The system doing what is needed, not what the loudest asked, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Requirements engineer
27%
AI can already do 27% of this job.
#187 / 763
View rankingRequirements 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 |
|---|---|---|---|
Workshop, the actor and the requirement.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Conflict, the loudest and not swallowing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Criterion, the test and not leaving it vague.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Change, the impact and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The project lead, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it is needed, and not the loudest one's.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
- requirements
- actor workshops
- acceptance criteria
- change impact
- backlog
- tests
- not swallow the loudest
- ambiguity
Sources for this job· O*NET 15-1299.00· ESCO/ISCO 2511
IS WORK OVER?
Security engineer
27%
#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