Automation index
How much of a Control engineer’s job can AI already do?
A PID comes earlier. The plant not oscillating without leaving it in manual for ever do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Control engineer
22%
AI can already do 22% of this job.
#397 / 763
View rankingControl 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 |
|---|---|---|---|
PID, tune and the model.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Plant, the swing and the one that runs away.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Mode, manual and not leaving it for ever.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Alarm, the interlock and not silencing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Operations, the recipe and not changing blind.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That it does not swing, and not leaving manual for ever.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- PID
- tune
- swings
- manual mode
- interlocks
- recipes
- control models
- not silence alarms
Sources for this job· O*NET 17-2199.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