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.
#333 / 763
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?
Backend developer
27%
#151 / 763
View rankingBackend 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 |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512