IS WORK OVER?

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

Petroleum 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
Reservoir, rate and the well programme.
Estimate

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

16%44%+7
Rig, mud and lost circulation.
Estimate

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

18%14%+2.5
Completion, tests and the ops report.
Estimate

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

16%36%+5.8
Production, water cut and the workover.
Estimate

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

16%28%+4.5
HSE, blowout and the drill that is not a game.
Estimate

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

18%16%+2.9
Not killing the well, and signing the programme.
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

  • 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

QA automation 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
Test, the selector and the flake.
Estimate

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

18%48%+8.6
Pipeline, the green and the one that lies.
Estimate

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

16%40%+6.4
Bug, the repro and not closing it blind.
Estimate

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

16%22%+3.5
Data, the environment and not sharing prod.
Estimate

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

16%28%+4.5
The developer, the rush and not skipping the one that fails.
Estimate

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

18%14%+2.5
Catch the bug, and not painting a lying green.
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

  • automated tests
  • selectors
  • flakes
  • QA pipelines
  • repro
  • environments
  • lying green
  • debug tests

Sources for this job· O*NET 15-1253.00· ESCO/ISCO 2519

Analyse my job

Jobs with similar scores

  1. 275Environmental engineer25%
  2. 276Biomedical engineer25%
  3. 277Civil engineer25%
  4. 279Production engineer25%
  5. 280Robotics engineer25%
  6. 281Telecom engineer25%