Automation index
How much of a Appliance technician’s job can AI already do?
An error code comes earlier. Diagnosing in someone else’s kitchen and leaving it washing do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Appliance technician
22%
AI can already do 22% of this job.
#385 / 633
View rankingAppliance 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 |
|---|---|---|---|
Code, history and the spare.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Strip, test and the built-in one.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
Order the part, second visit and the client who is out.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Warranty, misuse and what it does not cover.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The tight kitchen and not marking the unit.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Leave it washing, and not swapping the board blind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- diagnose appliances
- error codes
- strip built-ins
- spares
- warranty
- second visit
- test boards
- service call
Sources for this job· O*NET 49-9031.00· ESCO/ISCO 7412
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