IS WORK OVER?

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

Cultural 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.

TaskShareAIPoints
Programme, fees and the venue calendar.
Estimate

No public source provides a precise figure. This is our estimate.

16%44%+7
Grants, paperwork and sponsorship.
Estimate

No public source provides a precise figure. This is our estimate.

16%36%+5.8
Artists, crew and the day the sound dies.
Estimate

No public source provides a precise figure. This is our estimate.

18%16%+2.9
Audience, comms and what does not fill.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
The councillor, the clash and soft censorship.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
Pay on time, and not leaving culture in the spreadsheet.
Estimate

No public source provides a precise figure. This is our estimate.

16%14%+2.2
Total100%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

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 245Game designer26%
  2. 246Set designer26%
  3. 247Statistician26%
  4. 249Screenwriter26%
  5. 250Structural engineer26%
  6. 251Process engineer26%