IS WORK OVER?

Automation index

How much of a Radiation oncologist’s job can AI already do?

Assisted contouring comes earlier. Setting the field and not burning healthy tissue do not.

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

Task comparison

Radiation oncologist

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
Contouring, fractions and the dose plan.
Estimate

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

16%48%+7.7
Clinic, the tumour and what can be irradiated.
Estimate

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

18%18%+3.2
Simulation, immobilisation and the machine day.
Estimate

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

16%22%+3.5
Side effects, pauses and the patient who cannot take it.
Estimate

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

16%28%+4.5
Board, the surgeon and the medical oncologist.
Estimate

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

18%14%+2.5
Signing the plan and the dose that does not erase.
Estimate

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

16%12%+1.9
Total100%23%

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

Skills and activities

  • contouring
  • plan radiotherapy
  • dosimetry
  • RT simulation
  • fractions
  • tumour board
  • radiation effects
  • immobilise the patient

Sources for this job· O*NET 29-1224.00· ESCO/ISCO 2212

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. 354Pulmonologist23%
  2. 355Drone pilot23%
  3. 356Language teacher23%
  4. 358Rheumatologist23%
  5. 359Victim support worker23%
  6. 360Printer technician23%