IS WORK OVER?

Automation index

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

A diagram and an app come earlier. Wiring without false alarms and training the neighbour do not.

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

Task comparison

Alarm installer

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
Diagram, zones and programming the panel.
Estimate

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

16%40%+6.4
Wire, sensors and the detector that trips alone.
Estimate

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

18%14%+2.5
ARC, tests and the connection note.
Estimate

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

16%32%+5.1
Train the user and the fob that gets lost.
Estimate

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

16%22%+3.5
The lived-in flat, the brick and not breaking extra.
Estimate

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

18%18%+3.2
No false alarms, and a real call-out.
Estimate

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

16%12%+1.9
Total100%23%

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

Skills and activities

  • fit alarms
  • program panels
  • wire sensors
  • ARC
  • avoid false alarms
  • train the user
  • detectors
  • alarm zones

Sources for this job· O*NET 49-2098.00· ESCO/ISCO 7412

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. 343Haematologist23%
  2. 344Infectious disease physician23%
  3. 345Labour inspector23%
  4. 347Home-automation installer23%
  5. 348Station master23%
  6. 349Aircraft mechanic23%