IS WORK OVER?

Automation index

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

A network model comes earlier. The trench not going up without leaving the village without gas do not.

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

Task comparison

Gas network 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
Model, pressures and the diameter.
Estimate

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

16%40%+6.4
Trench, the weld and the one that was not x-rayed.
Estimate

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

18%14%+2.5
Leak, the detector and getting people out.
Estimate

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

16%28%+4.5
Cut, the bypass and not leaving them without gas.
Estimate

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

16%22%+3.5
The council, the rush and not covering without testing.
Estimate

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

18%18%+3.2
That the trench does not go up, and not leaving them without gas.
Estimate

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

16%12%+1.9
Total100%22%

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

Skills and activities

  • network pressures
  • diameters
  • trenches
  • gas welds
  • leaks
  • detectors
  • bypass
  • x-rays

Sources for this job· O*NET 17-2171.00· ESCO/ISCO 2145

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. 413Mining engineer22%
  2. 414Bridge engineer22%
  3. 415Commissioning engineer22%
  4. 417District heating engineer22%
  5. 418Safety engineer22%
  6. 419Welding engineer22%