Automation index
How much of a Criminal lawyer’s job can AI already do?
A defence brief comes earlier. Being in the cells at three without selling cheap innocence do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Criminal lawyer
27%
AI can already do 27% of this job.
#130 / 763
View rankingCriminal lawyer
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 |
|---|---|---|---|
File, evidence and the brief.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Cells, the statement and not leaving them alone.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Trial, the jury and not overplaying it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Sentence, the plea and not signing blind.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The family, the headline and not leaking.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Be there at three, and not selling cheap innocence.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
- case files
- statements
- criminal trials
- pleas
- cells
- evidence
- not leak
- defence briefs
Sources for this job· O*NET 23-1011.00· ESCO/ISCO 2611
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