IS WORK OVER?

Automation index

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

A PLC and a SCADA come earlier. Leaving the plant in auto without it tripping do not.

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

Task comparison

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
PLC, SCADA and the interlock.
Estimate

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

18%48%+8.6
Panel, loops and the lying sensor.
Estimate

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

16%22%+3.5
FAT, SAT and commissioning.
Estimate

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

16%36%+5.8
Recipes, batches and the product change.
Estimate

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

16%28%+4.5
The shift, the alarm and not bypassing the interlock.
Estimate

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

18%14%+2.5
That it does not trip, and documenting the program.
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

  • program PLCs
  • SCADA
  • interlocks
  • control loops
  • FAT SAT
  • commissioning
  • plant alarms
  • automation panels

Sources for this job· O*NET 17-3024.00· ESCO/ISCO 2149

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. 174Acoustics engineer27%
  2. 175Cloud engineer27%
  3. 176Food engineer27%
  4. 178HVAC engineer27%
  5. 179Cost engineer27%
  6. 180Energy engineer27%