Automation index
How much of a Reliability engineer’s job can AI already do?
An MTBF comes earlier. It not dropping at three without hiding the spare do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Reliability engineer
27%
AI can already do 27% of this job.
#182 / 763
View rankingReliability 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 |
|---|---|---|---|
Data, MTBF and the Pareto.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Failure, the cause and not patching twice.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Spare, the critical and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
RCM, the plan and the one that is not done.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Production, the rush and not running the tired one.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not drop at three, and not hiding the spare.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
- MTBF
- Pareto
- root causes
- critical spares
- RCM
- failures
- maintenance plans
- not patch twice
Sources for this job· O*NET 17-2112.00· ESCO/ISCO 2141
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