Automation index
How much of a Site reliability engineer’s job can AI already do?
A runbook and autoscale come earlier. The 3 a.m. incident without taking production down do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Site reliability engineer
28%
AI can already do 28% of this job.
#103 / 763
View rankingSite reliability 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 |
|---|---|---|---|
SLOs, alerts and the runbook.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Incident, war room and not making it worse.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI/CD, capacity and the error budget.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Postmortem, toil and automating the repeated.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The product that wants to ship and the SLO that will not allow it.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Not taking production down, and signing the change.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- SLOs
- runbooks
- handle incidents
- error budget
- autoscale
- postmortem
- reduce toil
- reliability CI/CD
Sources for this job· O*NET 15-1244.00· ESCO/ISCO 2512
IS WORK OVER?
Game developer
27%
#153 / 763
View rankingGame 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 |
|---|---|---|---|
Prototype, the loop and the input.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Physics, the bug and the one that teleports.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Build, the platform and the one that will not ship.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Frame, 30 and not leaving it at 8.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the fun and not cutting what it feels.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it plays, and not leaving the frame at 8.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
- game prototypes
- game loop
- input
- builds
- frames
- physics bugs
- platforms
- write game code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514