Automation index
How much of a Watchmaker’s job can AI already do?
A diagnosis and a spare come earlier. Opening the movement so it keeps time again do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Watchmaker
22%
AI can already do 22% of this job.
#376 / 633
View rankingWatchmaker
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 |
|---|---|---|---|
Diagnose, quote and explain to the client.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Open, strip, clean and oil the movement.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
Spares, rate adjustment and calibration.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Cases, straps, water resistance and polish.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The counter, commissions and pieces that do not come back.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Times, real spares and a watch that keeps time.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- repair watches
- open movements
- oil calibres
- adjust rate
- change straps
- water-resistance test
- diagnose watches
- polish cases
Sources for this job· O*NET 51-9071.00· ESCO/ISCO 7311
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