Automation index
How much of a Anthropologist’s job can AI already do?
A transcript and a code come earlier. Being in the field and not projecting too much do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Anthropologist
23%
AI can already do 23% of this job.
#287 / 623
View rankingAnthropologist
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 |
|---|---|---|---|
Transcribe, code and write.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Field, interviews and observation.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Archive, literature and research design.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Ethics, consent and communities.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Teaching, projects and outreach.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not extracting from people without giving anything back.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 23% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Transcribe, code and write
- Field, interviews and observation
- Archive, literature and research design
- Ethics, consent and communities
- Teaching, projects and outreach
- antropologo
- anthropologist
Sources for this job· O*NET 19-3091.00· ESCO/ISCO 2632
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