Automation index
How much of a Tow-truck driver’s job can AI already do?
A call and a route come earlier. Hooking on the hard shoulder without making the crash worse do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Tow-truck driver
20%
AI can already do 20% of this job.
#444 / 633
View rankingTow-truck driver
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 |
|---|---|---|---|
Call, route and the vehicle type.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Hard shoulder, hook and traffic that will not stop.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
Hydraulics, bed and the low car that scrapes.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Garage, the note and the client who argues.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Night, rain and not becoming the next crash.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Not making the crash worse, and signing the hook.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
- hook vehicles
- hard shoulder
- the bed
- recovery calls
- crane hydraulics
- recovery notes
- traffic
- low cars
Sources for this job· O*NET 53-3032.00· ESCO/ISCO 8332
IS WORK OVER?
Mobile developer
28%
#92 / 633
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.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
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514