Automation index
How much of a Orthodontist’s job can AI already do?
A digital setup and a first aligner come earlier. Bonding a bracket and not losing a tooth do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Orthodontist
22%
AI can already do 22% of this job.
#362 / 633
View rankingOrthodontist
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 |
|---|---|---|---|
Scan, cephalometry and a first setup.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Bond, adjust and review appliances.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Explain, motivate and follow the teenager.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Charts, photos and aligner orders.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Wire emergencies and lost brackets.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Final occlusion and not leaving a relapse.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Scan, cephalometry and a first setup
- Bond, adjust and review appliances
- Explain, motivate and follow the teenager
- Charts, photos and aligner orders
- Wire emergencies and lost brackets
- Final occlusion and not leaving a relapse
- ortodoncista
- orthodontist
Sources for this job· O*NET 29-1023.00· ESCO/ISCO 2261
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