IS WORK OVER?

Automation index

How much of a Forensic scientist’s job can AI already do?

A lab protocol comes earlier. A result that holds in court without contaminating do not.

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

Task comparison

Forensic scientist

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
Protocol, chain and the sample.
Estimate

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

16%40%+6.4
Analyse, the blank and the one that contaminates.
Estimate

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

18%14%+2.5
Report, the link and not jumping.
Estimate

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

16%28%+4.5
Court, the lawyer and holding.
Estimate

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

16%22%+3.5
Police haste and not skipping the blank.
Estimate

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

18%18%+3.2
Hold in court, and not contaminating.
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

  • chain of custody
  • blanks
  • forensic samples
  • the link
  • the hearing
  • lab protocols
  • expert reports
  • contamination

Sources for this job· O*NET 19-4092.00· ESCO/ISCO 3119

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. 372School librarian22%
  2. 373Botanist22%
  3. 374Chocolatier22%
  4. 376Hotel concierge22%
  5. 377Transplant coordinator22%
  6. 378Embedded developer22%