Automation index
How much of a Pathologist’s job can AI already do?
A first slice and a code come earlier. Putting the diagnosis the chemo depends on do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Pathologist
30%
AI can already do 30% of this job.
#44 / 763
View rankingPathologist
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 |
|---|---|---|---|
Grossing, embedding and the first trim.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Read stains, IHC and a template report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 52% | +8.3 |
The hard case, the second look and the frozen section.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Board, the surgeon on the phone and the margin.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Cytology, autopsy and the specimen that arrives late.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Signing the diagnosis and what the patient is playing for.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 30% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- read biopsies
- grossing
- immunohistochemistry
- frozen section
- pathology report
- cytology
- surgical margins
- autopsy
Sources for this job· O*NET 29-1222.00· ESCO/ISCO 2212
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