Automation index
How much of a Last-mile manager’s job can AI already do?
A zone map comes earlier. Hitting the peak without leaving the neighbourhood without a courier do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Last-mile manager
26%
AI can already do 26% of this job.
#257 / 763
View rankingLast-mile manager
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 |
|---|---|---|---|
Zones, capacity and route cuts.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
KPIs, first attempt and incidents.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
The courier, the lobby and the one who will not open.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Peaks, rain and hiring too many or too few.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The angry customer and not dressing delivered.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Cover the peak, and not leaving the neighbourhood orphaned.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- delivery zones
- first attempt
- delivery KPIs
- last-mile peaks
- lobbies
- delivery incidents
- courier capacity
- cut routes
Sources for this job· O*NET 11-3071.00· ESCO/ISCO 1324
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