Automation index
How much of a Cycle courier’s job can AI already do?
A job app comes earlier. Crossing the city and delivering it whole do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Cycle courier
20%
AI can already do 20% of this job.
#466 / 643
View rankingCycle courier
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 |
|---|---|---|---|
App, routes and the urgent job.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Pedal, traffic and not losing the parcel.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
Lobby, the code and the one who will not come down.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Rain, puncture and the job that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The platform, the fee and the one that does not pay time.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Deliver it whole, and not leaving it on the landing blind.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 20% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- cycle courier
- urgent jobs
- lobbies
- punctures
- courier app
- city traffic
- platform fees
- not lose the parcel
Sources for this job· O*NET 43-5021.00· ESCO/ISCO 8321
IS WORK OVER?
Technical writer
28%
#115 / 643
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.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
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641