Automation index
How much of a Printer technician’s job can AI already do?
A jam log comes earlier. Leaving the office printing without inking the floor do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Printer technician
23%
AI can already do 23% of this job.
#314 / 623
View rankingPrinter technician
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, count and the maintenance kit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Jam, fuser and toner on the floor.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Network, queues and the wrong driver.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Contract, visits and the machine that is done.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The office at peak and not stopping invoicing.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That it prints, and not swapping the fuser blind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 23% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- jams
- fuser
- maintenance kits
- print queues
- toner
- service contracts
- drivers
- copy counts
Sources for this job· O*NET 49-2011.00· ESCO/ISCO 7421
IS WORK OVER?
Mobile developer
28%
#92 / 623
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