Automation index
How much of a Cultural manager’s job can AI already do?
A programme and a budget come earlier. Filling the room and paying the people who make it do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Cultural manager
26%
AI can already do 26% of this job.
#248 / 763
View rankingCultural manager
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 |
|---|---|---|---|
Programme, fees and the venue calendar.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
Grants, paperwork and sponsorship.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Artists, crew and the day the sound dies.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Audience, comms and what does not fill.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The councillor, the clash and soft censorship.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Pay on time, and not leaving culture in the spreadsheet.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
- programme culture
- artist fees
- justify grants
- fill the room
- sponsorship
- deal with artists
- cultural comms
- venue budget
Sources for this job· O*NET 27-1029.00· ESCO/ISCO 2431
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