IS WORK OVER?

Automation index

How much of a Crime scene technician’s job can AI already do?

A trace protocol comes earlier. Not contaminating the scene so it holds up in court do not.

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

Task comparison

Crime scene technician

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
Inspection, photos and the scene sketch.
Estimate

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

16%36%+5.8
Collect traces, prints and the DNA that gets walked on.
Estimate

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

18%12%+2.2
Chain of custody, labels and the lab.
Estimate

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

16%32%+5.1
Report, reconstruction and the file.
Estimate

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

16%28%+4.5
The dirty scene, the rush and the one who enters ungloved.
Estimate

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

18%18%+3.2
That it holds in court, and not breaking the chain.
Estimate

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

16%14%+2.2
Total100%23%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • collect traces
  • fingerprints
  • chain of custody
  • photograph scenes
  • forensic DNA
  • scene sketch
  • police lab
  • not contaminate

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

QA automation engineer

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
Test, the selector and the flake.
Estimate

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

18%48%+8.6
Pipeline, the green and the one that lies.
Estimate

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

16%40%+6.4
Bug, the repro and not closing it blind.
Estimate

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

16%22%+3.5
Data, the environment and not sharing prod.
Estimate

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

16%28%+4.5
The developer, the rush and not skipping the one that fails.
Estimate

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

18%14%+2.5
Catch the bug, and not painting a lying green.
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

  • automated tests
  • selectors
  • flakes
  • QA pipelines
  • repro
  • environments
  • lying green
  • debug tests

Sources for this job· O*NET 15-1253.00· ESCO/ISCO 2519

Analyse my job

Jobs with similar scores

  1. 368Rheumatologist23%
  2. 369Victim support worker23%
  3. 370Printer technician23%
  4. 372CCTV technician23%
  5. 373Aquaculturist22%
  6. 374Insulation installer22%