Automation index
How much of a Transplant coordinator’s job can AI already do?
A donor protocol comes earlier. Talking to the family at three in the morning do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Transplant coordinator
22%
AI can already do 22% of this job.
#377 / 763
View rankingTransplant coordinator
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 |
|---|---|---|---|
Alert, the donor and the protocol.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
ICU, brain death and the one who doubts.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Family, three in the morning and not pushing.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Logistics, the retrieval team and the plane.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Theatre, the ischaemia time and not losing the organ.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Talk to the family, and not pushing.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
- donors
- brain death
- family consent
- retrieval teams
- ischaemia time
- ICU
- organ logistics
- not push
Sources for this job· O*NET 29-1141.00· ESCO/ISCO 2269
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