IS WORK OVER?

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

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

TaskShareAIPoints
Plan, IGRT and the day’s set-up.
Estimate

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

16%40%+6.4
Immobilise, tattoo and treat fraction by fraction.
Estimate

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

22%12%+2.6
Check images, shifts and call the physician.
Estimate

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

16%28%+4.5
Side effects, the patient who cries and the wait.
Estimate

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

16%22%+3.5
Machine QA and alarms.
Estimate

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

16%32%+5.1
Today’s dose and not irradiating the wrong thing.
Estimate

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

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

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. 326Property valuer24%
  2. 327Hearing aid technician24%
  3. 328Job insertion technician24%
  4. 330Surveyor24%
  5. 331Urban planner24%
  6. 332Allergist23%