Automation index
How much of a Palliative care doctor’s job can AI already do?
A pain scale comes earlier. Being in the room when curative treatment stops do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Palliative care doctor
22%
AI can already do 22% of this job.
#443 / 773
View rankingPalliative care doctor
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 |
|---|---|---|---|
Pain, the scale and the rescue dose.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The room, the family and the one who will not hear.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Symptom, the route and not over-sedating.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The team, the home discharge and the weekend.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The oncologist, the limit and not walking away.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Be there, and not leaving the end alone.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
- pain scales
- opioid rescue
- palliative sedation
- home discharge
- refractory symptoms
- grieving family
- subcutaneous route
- end of life
Sources for this job· O*NET 29-1229.00· ESCO/ISCO 2212
IS WORK OVER?
Backend developer
27%
#153 / 773
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