IS WORK OVER?

Automation index

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

Searching records and a report come earlier. Following someone, believing a witness, and not burning the case do not.

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

Task comparison

Detective

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
Search records, cameras and files.
Estimate

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

20%42%+8.4
Reports, timelines and court requests.
Estimate

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

16%35%+5.6
Surveillance, interviews and the scene.
Estimate

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

18%12%+2.2
Weigh a witness and a false lead.
Estimate

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

16%10%+1.6
Coordinate with prosecutors and units.
Estimate

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

16%14%+2.2
Decide the next step and keep the file closed.
Estimate

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

14%16%+2.2
Total100%22%

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

Skills and activities

  • police report
  • patrol
  • identify a person
  • Search records, cameras and files
  • Reports, timelines and court requests
  • Surveillance, interviews and the scene
  • Weigh a witness and a false lead
  • Coordinate with prosecutors and units
  • detective
  • investigador privado

Sources for this job· O*NET 33-3021.00· ESCO/ISCO 5412

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. 376Hotel concierge22%
  2. 377Transplant coordinator22%
  3. 378Embedded developer22%
  4. 380Diplomat22%
  5. 381Funeral director22%
  6. 382Dosimetrist22%