Automation index
How much of a Archaeologist’s job can AI already do?
A report and a sheet come earlier. Digging and not breaking the context do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Archaeologist
22%
AI can already do 22% of this job.
#320 / 623
View rankingArchaeologist
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 |
|---|---|---|---|
Sheets, drawing and the intervention report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Excavate, sieve and record units.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Authorities, developer and site deadlines.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Lab, dating and publication.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Store, conservation and outreach.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not losing a context by going too fast.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
- Excavate, sieve and record units
- Authorities, developer and site deadlines
- Lab, dating and publication
- Store, conservation and outreach
- Not losing a context by going too fast
- arqueologo
- archaeologist
Sources for this job· O*NET 19-3091.00· ESCO/ISCO 2632
IS WORK OVER?
Web developer
26%
#198 / 623
View rankingWeb 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 |
|---|---|---|---|
Layout, components and API consumption.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 48% | +9.6 |
Accessibility, performance and technical SEO.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Design, product and the client who changes their mind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Deploys, incidents and monitoring.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Tests, code review and documentation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not shipping a half-change on a Friday.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- write code
- programming
- software development
- coding
- debug code
- Layout, components and API consumption
- Deploys, incidents and monitoring
- Tests, code review and documentation
- Not shipping a half-change on a Friday
- desarrollador web
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513