IS WORK OVER?

Automation index

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

A diagram and a balance come earlier. Stopping the plant and not overloading the reactor do not.

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

Task comparison

Process 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
P&IDs, balances and the operating procedure.
Estimate

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

18%48%+8.6
Plant, trials and the real bottleneck.
Estimate

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

16%22%+3.5
Capacity, yields and the improvement report.
Estimate

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

16%40%+6.4
Start-up, shutdown and the shift that skips the SOP.
Estimate

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

16%18%+2.9
Process safety and the HAZOP that hurts.
Estimate

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

18%14%+2.5
Not overloading the reactor, and signing the change.
Estimate

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

16%12%+1.9
Total100%26%

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

Skills and activities

  • P&IDs
  • mass balances
  • HAZOP
  • plant start-up
  • improve yields
  • SOP
  • bottlenecks
  • process safety

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. 248Cultural manager26%
  2. 249Screenwriter26%
  3. 250Structural engineer26%
  4. 252Midwife26%
  5. 253Penetration tester26%
  6. 254Court-appointed expert26%