IS WORK OVER?

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

Waste 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.

TaskShareAIPoints
Code, characterise and the paper.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Plant, the mix and the one you cannot.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
Move, the haulier and the note.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Inspection, the tip and not hiding.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
The producer, the saving and not diluting.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
Where it should, not next door.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 496Maintenance technician22%
  2. 497Environmental technician22%
  3. 498Metrology technician22%
  4. 500Irrigation technician22%
  5. 501Environmental health officer22%
  6. 502Public health officer22%