Automation index
How much of a Piano tuner’s job can AI already do?
An octave protocol comes earlier. Leaving the piano in tune for the concert do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Piano tuner
19%
AI can already do 19% of this job.
#474 / 633
View rankingPiano tuner
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, pinblock and the protocol.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Tune, octaves and the unison.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
Regulate, dampers and the one that will not cut.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Voicing, hammers and the one that is hard.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The concert, the hall and not leaving it flat.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
In tune, and lasting the concert.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 19% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- tune pianos
- octaves
- unisons
- dampers
- pinblock
- voicing
- hammers
- regulate action
Sources for this job· O*NET 49-9063.00· ESCO/ISCO 7312
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