Automation index
How much of a Lathe operator’s job can AI already do?
A CNC run and a pass come earlier. Setting up, measuring and not scrapping the part do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Lathe operator
26%
AI can already do 26% of this job.
#260 / 763
View rankingLathe operator
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 |
|---|---|---|---|
Read the drawing, tolerances and the route card.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Set up, clamp, pick the tool and the origin.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Turn, face, thread and finish the part.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 28% | +5 |
Measure, tweak offsets and not scrap the batch.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Lathe care, swarf and safety.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Grades, times and liability for the dimension.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- turn parts
- set up the lathe
- measure dimensions
- cut threads
- adjust offsets
- read mechanical drawings
- avoid scrap
- pick tools
Sources for this job· O*NET 51-4034.00· ESCO/ISCO 7223
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