Automation index
How much of a Waste technician’s job can AI already do?
A waste code comes earlier. The waste going where it should, not the next bin, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Waste technician
22%
AI can already do 22% of this job.
#392 / 633
View rankingWaste technician
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 |
|---|---|---|---|
Code, characterise and the paper.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Plant, the mix and the one you cannot.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Move, the haulier and the note.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Inspection, the tip and not hiding.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The producer, the saving and not diluting.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Where it should, not next door.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
- waste codes
- characterise waste
- transfer notes
- the tip
- mixing
- producers
- waste papers
- not dilute
Sources for this job· O*NET 19-4042.00· ESCO/ISCO 2143
IS WORK OVER?
Mobile developer
28%
#92 / 633
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