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
IS WORK OVER?
Crime scene technician
23%
AI can already do 23% of this job.
#315 / 623
View rankingCrime 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.
| Task | Share | AI | Points |
|---|---|---|---|
Inspection, photos and the scene sketch.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Collect traces, prints and the DNA that gets walked on.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
Chain of custody, labels and the lab.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Report, reconstruction and the file.EstimateNo 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.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That it holds in court, and not breaking the chain.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 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
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514