Automation index
How much of a Historian’s job can AI already do?
A corpus and a chronology come earlier. Going to the archive, reading the hand, and deciding what is a fact do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Historian
25%
AI can already do 25% of this job.
#227 / 623
View rankingHistorian
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 |
|---|---|---|---|
Search, transcribe and sort sources.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 45% | +9 |
Draft chapters, cards and bibliography.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 38% | +6.8 |
Archive work and source criticism.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 15% | +2.7 |
Argue the thesis and debate peers.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
Teaching, outreach and museums.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
Choose the cut and the question.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 14% | +2 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Search, transcribe and sort sources
- Draft chapters, cards and bibliography
- Archive work and source criticism
- Argue the thesis and debate peers
- Teaching, outreach and museums
- Choose the cut and the question
- historiador
- historian
Sources for this job· O*NET 19-3093.00· ESCO/ISCO 2633
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