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
IS WORK OVER?
Dosimetrist
22%
AI can already do 22% of this job.
#382 / 763
View rankingDosimetrist
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 |
|---|---|---|---|
CT, contours and the plan.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Organ at risk, the curve and not overshooting.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Physics, the check and the one that does not fit.EstimateNo 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.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The oncologist, the trade-off and not signing blind.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
The tumour gets it, and the healthy organ does not.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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
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