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
IS WORK OVER?
Process engineer
26%
AI can already do 26% of this job.
#205 / 633
View rankingProcess 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.
| Task | Share | AI | Points |
|---|---|---|---|
P&IDs, balances and the operating procedure.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Plant, trials and the real bottleneck.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Capacity, yields and the improvement report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Start-up, shutdown and the shift that skips the SOP.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Process safety and the HAZOP that hurts.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Not overloading the reactor, and signing the change.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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.
| Task | Share | AI | Points |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641