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
IS WORK OVER?
Radio host
22%
AI can already do 22% of this job.
#347 / 633
View rankingRadio 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.
| Task | Share | AI | Points |
|---|---|---|---|
Rundown, clips and a first script.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
On air, interviews and a silence that weighs.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Guests, producer and real time.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Edit, podcast and the show’s socials.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Voice, shifts and not going blank.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not saying something you cannot take back.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 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
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641