Automation index
How much of a Route planner’s job can AI already do?
An optimiser comes earlier. Fitting the windows without blowing the hours do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Route planner
28%
AI can already do 28% of this job.
#112 / 763
View rankingRoute planner
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 |
|---|---|---|---|
Optimise, windows and capacity.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Restrictions, tolls and the right vehicle.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The salesperson who promises and the plan that will not.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Recalc, incidents and the next day.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The warehouse, the cut-off and not leaving the last one.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it fits, and not blowing the hours.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
- optimise routes
- delivery windows
- tolls
- vehicle capacity
- recalc
- traffic restrictions
- warehouse cut-off
- driving hours
Sources for this job· O*NET 13-1081.00· ESCO/ISCO 4323
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