Automation index
How much of a Heritage interpreter’s job can AI already do?
A tour script comes earlier. Them looking at the stone and not just the phone do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Heritage interpreter
22%
AI can already do 22% of this job.
#429 / 773
View rankingHeritage interpreter
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 |
|---|---|---|---|
Script, the group and the time.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Room, the question and the one who will not listen.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
The piece, the context and not making it up.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
School group, the yard and getting them to touch carefully.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The director, capacity and not overcrowding.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That they look at the stone, and not just the phone.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- tour scripts
- school groups
- pieces
- historical context
- capacity
- not make it up
- heritage
- guided visits
Sources for this job· O*NET 25-4012.00· ESCO/ISCO 2621
IS WORK OVER?
Backend developer
27%
#153 / 773
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