IS WORK OVER?

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

Duty 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.

TaskShareAIPoints
Appointment, the court and the deadline.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Cells, the statement and actually reading it.
Estimate

No 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.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Hearing, the judge and not staying quiet.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
The bar, the fee and not dropping the case.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
Get there, and not wrapping it in ten minutes.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%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

Analyse my job

Jobs with similar scores

  1. 430Court interpreter22%
  2. 431Banquet manager22%
  3. 432Table official22%
  4. 434Radio host22%
  5. 435Olive-oil miller22%
  6. 436Special-education teacher22%