Automation index
How much of a Automation engineer’s job can AI already do?
A PLC and a SCADA come earlier. Leaving the plant in auto without it tripping do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Automation engineer
27%
AI can already do 27% of this job.
#159 / 623
View rankingAutomation 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 |
|---|---|---|---|
PLC, SCADA and the interlock.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Panel, loops and the lying sensor.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
FAT, SAT and commissioning.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Recipes, batches and the product change.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The shift, the alarm and not bypassing the interlock.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not trip, and documenting the program.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
- program PLCs
- SCADA
- interlocks
- control loops
- FAT SAT
- commissioning
- plant alarms
- automation panels
Sources for this job· O*NET 17-3024.00· ESCO/ISCO 2149
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.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
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514