Automation index
How much of a ML engineer’s job can AI already do?
Training a baseline and a notebook is fast. Shipping it, watching drift, and owning the miss is not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
ML engineer
29%
AI can already do 29% of this job.
#64 / 623
View rankingML 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 |
|---|---|---|---|
Train models, features and notebooks.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 48% | +10.6 |
Evaluate, document and compare runs.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 42% | +7.6 |
Deploy, monitor and retrain.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Talk to product about what a good error is.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
Dirty data, bias and model limits.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 18% | +2.5 |
On-call, incidents and rollback.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 29% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Train models, features and notebooks
- Evaluate, document and compare runs
- Deploy, monitor and retrain
- Talk to product about what a good error is
- Dirty data, bias and model limits
- On-call, incidents and rollback
- machine learning engineer
- ingeniero ml
- mlops
Sources for this job· O*NET 15-1221.00· ESCO/ISCO 2511
IS WORK OVER?
Technical writer
28%
#115 / 623
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.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
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641