Automation index
How much of a Radiation therapist’s job can AI already do?
Guided set-up comes earlier. Immobilising every day and not missing the field do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Radiation therapist
24%
AI can already do 24% of this job.
#329 / 763
View rankingRadiation therapist
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 |
|---|---|---|---|
Plan, IGRT and the day’s set-up.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Immobilise, tattoo and treat fraction by fraction.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 12% | +2.6 |
Check images, shifts and call the physician.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Side effects, the patient who cries and the wait.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Machine QA and alarms.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Today’s dose and not irradiating the wrong thing.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 14% | +2 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- set up for RT
- IGRT
- immobilise patients
- deliver fractions
- linac QA
- reference tattoos
- shifts
- radiotherapy
Sources for this job· O*NET 29-1124.00· ESCO/ISCO 3211
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