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.
#278 / 763
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?
Backend developer
27%
#151 / 763
View rankingBackend 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.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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