Automation index
How much of a Legal secretary’s job can AI already do?
A stock filing comes earlier. The deadline not dying and counsel having the paper do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Legal secretary
27%
AI can already do 27% of this job.
#214 / 763
View rankingLegal secretary
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 |
|---|---|---|---|
Filings, deadlines and the court.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Appointments, the client and the one who is late.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Copies, notices and the procurator.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Bill, the procurator and not losing the receipt.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Counsel, the rush and not sending the draft.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
The deadline alive, and the paper at court.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
- filings
- procedural deadlines
- notices
- procurator
- office appointments
- copies
- receipts
- the court
Sources for this job· O*NET 43-6012.00· ESCO/ISCO 3343
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