Automation index
How much of a Duty solicitor’s job can AI already do?
An appointment comes earlier. Getting to the cells without wrapping it in ten minutes do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Duty solicitor
22%
AI can already do 22% of this job.
#433 / 773
View rankingDuty solicitor
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 |
|---|---|---|---|
Appointment, the court and the deadline.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Cells, the statement and actually reading it.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Duty, the small hours and the one who does not understand.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Hearing, the judge and not staying quiet.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The bar, the fee and not dropping the case.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Get there, and not wrapping it in ten minutes.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
- duty scheme
- appointments
- cells
- duty nights
- fees
- statements
- duty court
- not drop the case
Sources for this job· O*NET 23-1011.00· ESCO/ISCO 2611
IS WORK OVER?
Backend developer
27%
#153 / 773
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