IS WORK OVER?

Automation index

How much of a Radio host’s job can AI already do?

A rundown and a clip come earlier. Filling the air when the line drops does not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Radio host

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
Rundown, clips and a first script.
Estimate

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

16%40%+6.4
On air, interviews and a silence that weighs.
Estimate

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

20%12%+2.4
Guests, producer and real time.
Estimate

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

16%22%+3.5
Edit, podcast and the show’s socials.
Estimate

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

16%28%+4.5
Voice, shifts and not going blank.
Estimate

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

16%16%+2.6
Not saying something you cannot take back.
Estimate

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

16%14%+2.2
Total100%22%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • Rundown, clips and a first script
  • Guests, producer and real time
  • Edit, podcast and the show’s socials
  • Voice, shifts and not going blank
  • Not saying something you cannot take back
  • locutor
  • locutora
  • radio host

Sources for this job· O*NET 27-3011.00· ESCO/ISCO 2656

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. 431Banquet manager22%
  2. 432Table official22%
  3. 433Duty solicitor22%
  4. 435Olive-oil miller22%
  5. 436Special-education teacher22%
  6. 437Early-years teacher22%