Automation index
How much of a Museum curator’s job can AI already do?
An inventory and a wall text come earlier. What goes on show, and not damaging the piece, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Museum curator
23%
AI can already do 23% of this job.
#337 / 763
View rankingMuseum curator
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 |
|---|---|---|---|
Inventory, catalogue and write wall texts.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Curate, select and negotiate loans.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Install, lighting and preventive conservation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Research, publications and dossiers.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Public, tours and the board.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Not losing a piece or a wrong attribution.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
- Inventory, catalogue and write wall texts
- Curate, select and negotiate loans
- Research, publications and dossiers
- Public, tours and the board
- Not losing a piece or a wrong attribution
- conservador de museo
- curator
- comisario de exposicion
Sources for this job· O*NET 25-4012.00· ESCO/ISCO 2621
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