Automation index
How much of a Criminologist’s job can AI already do?
A crime map comes earlier. Understanding why it happens there, and what to do with the repeat offender, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Criminologist
29%
AI can already do 29% of this job.
#57 / 763
View rankingCriminologist
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 |
|---|---|---|---|
Data, maps and the victimisation report.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Profiles, reoffending and programme evaluation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Field, interviews and what the spreadsheet misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Police, judges and the measure under debate.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Prevention, the neighbourhood and the programme that does not fit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The opinion, and not selling magic recipes.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- crime maps
- study reoffending
- victimisation
- evaluate programmes
- situational prevention
- criminological profiles
- reports for judges
- fieldwork
Sources for this job· O*NET 19-3041.00· ESCO/ISCO 2632
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