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
IS WORK OVER?
Gas network engineer
22%
AI can already do 22% of this job.
#416 / 773
View rankingGas 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.
| Task | Share | AI | Points |
|---|---|---|---|
Model, pressures and the diameter.EstimateNo 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.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Leak, the detector and getting people out.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Cut, the bypass and not leaving them without gas.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The council, the rush and not covering without testing.EstimateNo 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.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 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
IS WORK OVER?
Backend developer
27%
#153 / 773
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