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 / 633
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?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.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
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641