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.
#177 / 763
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?
Backend developer
27%
#151 / 763
View rankingBackend 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 |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, 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 takes the spike, and not leaving the key.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
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512