IS WORK OVER?

Automation index

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

A dose plan comes earlier. The tumour getting it and the healthy organ not, for real, do not.

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

Task comparison

Dosimetrist

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
CT, contours and the plan.
Estimate

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

16%40%+6.4
Organ at risk, the curve and not overshooting.
Estimate

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

18%14%+2.5
Physics, the check and the one that does not fit.
Estimate

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

16%28%+4.5
Fraction, the setup and the patient who is not the same.
Estimate

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

16%22%+3.5
The oncologist, the trade-off and not signing blind.
Estimate

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

18%18%+3.2
The tumour gets it, and the healthy organ does not.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • dose plans
  • contours
  • organs at risk
  • dosimetry check
  • fractions
  • setup
  • sim CT
  • DVH curves

Sources for this job· O*NET 29-2036.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. 379Detective22%
  2. 380Diplomat22%
  3. 381Funeral director22%
  4. 383Section supervisor22%
  5. 384Debate coach22%
  6. 385School sports coach22%