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.
#499 / 773
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?
Backend developer
27%
#153 / 773
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