IS WORK OVER?

Automation index

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

An OEE and a sequencer come earlier. Getting the shift out without stopping the line for nothing do not.

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

Task comparison

Production 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
OEE, sequence and the shift plan.
Estimate

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

18%48%+8.6
Line, changeovers and the micro-stop.
Estimate

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

16%22%+3.5
Layout, times and the work standard.
Estimate

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

16%36%+5.8
Supervisors, unions and the shift that turns.
Estimate

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

16%18%+2.9
In-line quality and the batch that cannot ship.
Estimate

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

18%14%+2.5
Hit the plan, and not dressing the OEE.
Estimate

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

16%12%+1.9
Total100%25%

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

Skills and activities

  • OEE
  • sequence production
  • changeovers
  • layout
  • work standards
  • micro-stops
  • shift plan
  • in-line quality

Sources for this job· O*NET 17-2112.00· ESCO/ISCO 2141

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. 276Biomedical engineer25%
  2. 277Civil engineer25%
  3. 278Petroleum engineer25%
  4. 280Robotics engineer25%
  5. 281Telecom engineer25%
  6. 282Electrical engineer25%