IS WORK OVER?

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

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

TaskShareAIPoints
Script, the group and the time.
Estimate

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

16%40%+6.4
Room, the question and the one who will not listen.
Estimate

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

18%14%+2.5
The piece, the context and not making it up.
Estimate

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

16%28%+4.5
School group, the yard and getting them to touch carefully.
Estimate

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

16%22%+3.5
The director, capacity and not overcrowding.
Estimate

No 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.
Estimate

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

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

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. 426Welding inspector22%
  2. 427EV charger installer22%
  3. 428Social integrator22%
  4. 430Court interpreter22%
  5. 431Banquet manager22%
  6. 432Table official22%