IS WORK OVER?

Automation index

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

A ladder comes earlier. The machine stopping on a fault without jumping the e-stop do not.

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

Task comparison

PLC programmer

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
Ladder, tags and the comment.
Estimate

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

16%40%+6.4
Cell, the fault and the one that will not stop.
Estimate

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

18%14%+2.5
E-stop, the cable and not jumping it.
Estimate

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

16%28%+4.5
Recipe, the change and not dumping production.
Estimate

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

16%22%+3.5
The electrician, the terminals and going down to see it.
Estimate

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

18%18%+3.2
That it stops on a fault, and not jumping the e-stop.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • program PLCs
  • tags
  • e-stops
  • faults
  • recipes
  • terminals
  • program comments
  • not jump e-stops

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514

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. 470Art teacher22%
  2. 471Secondary teacher22%
  3. 472Private tutor22%
  4. 474Sales promoter22%
  5. 475Dental technician22%
  6. 476School psychologist22%