IS WORK OVER?

Automation index

How much of a Court interpreter’s job can AI already do?

A glossary comes earlier. Saying exactly what was said, not what suited, do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Court interpreter

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
Glossary, the case and the language.
Estimate

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

16%40%+6.4
Court, the oath and the one who stumbles.
Estimate

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

18%14%+2.5
Cells, the statement and not softening it.
Estimate

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

16%28%+4.5
Document, the translation and the stamp.
Estimate

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

16%22%+3.5
Counsel, the rush and not jumping a meaning.
Estimate

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

18%18%+3.2
Say what was said, and not what suited.
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

  • court glossaries
  • court interpreting
  • statements
  • the oath
  • sworn translation
  • cells
  • not soften
  • stamps

Sources for this job· O*NET 27-3091.00· ESCO/ISCO 2643

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. 427EV charger installer22%
  2. 428Social integrator22%
  3. 429Heritage interpreter22%
  4. 431Banquet manager22%
  5. 432Table official22%
  6. 433Duty solicitor22%