Automation index
How much of a Petroleum engineer’s job can AI already do?
A reservoir model comes earlier. Drilling without killing the well do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Petroleum engineer
25%
AI can already do 25% of this job.
#232 / 633
View rankingPetroleum 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 |
|---|---|---|---|
Reservoir, rate and the well programme.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
Rig, mud and lost circulation.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Completion, tests and the ops report.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Production, water cut and the workover.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
HSE, blowout and the drill that is not a game.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Not killing the well, and signing the programme.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- model reservoirs
- well programmes
- drilling mud
- completion
- workover
- water cut
- well HSE
- production tests
Sources for this job· O*NET 17-2171.00· ESCO/ISCO 2146
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