Automation index
How much of a In-house counsel’s job can AI already do?
A stock contract comes earlier. Saying no to sales without leaving the company sold do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
In-house counsel
27%
AI can already do 27% of this job.
#127 / 763
View rankingIn-house counsel
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 |
|---|---|---|---|
Contract, clauses and the risk.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Sales, the close and not yielding the essential.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Dispute, the procurator and not sleeping the deadline.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Board, the memo and not dressing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The CEO, the rush and not signing blind.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Say no, and not leaving the company sold.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
- commercial contracts
- clauses
- legal risk
- the board
- procedural deadlines
- sales
- not sign blind
- legal memos
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