Automation index
How much of a Neuropsychologist’s job can AI already do?
A battery comes earlier. Saying what is left of the person without scaring the family do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Neuropsychologist
27%
AI can already do 27% of this job.
#201 / 763
View rankingNeuropsychologist
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 |
|---|---|---|---|
Battery, norms and the report.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Patient, the fatigue and the one who quits the test.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Imaging, the lobe and not forcing the figure.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Rehab, the aim and what still can.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The family, the report and not scaring.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Say what is left, and not selling an extra diagnosis.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
- neuropsych batteries
- test norms
- cognitive rehab
- neuropsych reports
- test fatigue
- lobes
- the family
- not scare
Sources for this job· O*NET 19-3039.00· ESCO/ISCO 2634
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