Automation index
How much of a Pesticide applicator’s job can AI already do?
A farm log comes earlier. Treating without taking the neighbour or the river do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Pesticide applicator
22%
AI can already do 22% of this job.
#366 / 763
View rankingPesticide applicator
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 |
|---|---|---|---|
Log, product and the dose.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Apply, drift and the wind that gets up.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
The withholding period and the one who wants in now.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
PPE, the container and the collection point.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The neighbour, the bees and stopping in time.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Not taking the river, and signing the treatment.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
- farm log
- pesticide dose
- drift
- withholding period
- PPE
- empty containers
- bees
- field wind
Sources for this job· O*NET 37-3012.00· ESCO/ISCO 6113
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