IS WORK OVER?

Automation index

How much of a Home-automation installer’s job can AI already do?

A scene comes earlier. The house obeying without going dark do not.

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

Task comparison

Home-automation 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, buses and scene programming.
Estimate

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

16%40%+6.4
Wire, sensors and the switch that does not answer.
Estimate

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

18%14%+2.5
Integrate lights, climate and the client app.
Estimate

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

16%32%+5.1
Train, guest mode and the one who breaks it.
Estimate

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

16%22%+3.5
The lived-in house and not leaving it dark.
Estimate

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

18%18%+3.2
That it obeys, and not needing the cloud for a switch.
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

  • program scenes
  • home buses
  • integrate climate
  • sensors
  • home app
  • switches
  • guest mode
  • wire KNX

Sources for this job· O*NET 47-2111.00· ESCO/ISCO 7411

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. 344Infectious disease physician23%
  2. 345Labour inspector23%
  3. 346Alarm installer23%
  4. 348Station master23%
  5. 349Aircraft mechanic23%
  6. 350Family doctor23%