Automation index
How much of a Hydraulic engineer’s job can AI already do?
A floodplain model comes earlier. Sizing the channel so the village does not flood do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Hydraulic engineer
27%
AI can already do 27% of this job.
#190 / 763
View rankingHydraulic 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 |
|---|---|---|---|
Hydrology, flows and the floodplain model.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Field, section and what LiDAR misses.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Drainage works, pumps and the outfall.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Water permits and the river authority.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The flood, the village and the yes to the channel.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not flood, and not trusting the model alone.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
- model floodplains
- flows
- drainage
- channel works
- water permits
- pumps
- channel sections
- river authority
Sources for this job· O*NET 17-2051.00· ESCO/ISCO 2142
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