Automation index
How much of a Hydrologist’s job can AI already do?
A hydrograph comes earlier. Calling the rise without leaving the village blind do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Hydrologist
22%
AI can already do 22% of this job.
#339 / 633
View rankingHydrologist
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 |
|---|---|---|---|
Hydrograph, catchment and the model.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Field, gauging and the one that does not read.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Flood, the alert and not delaying.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Low flow, irrigation and the clash.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The authority, the figure and not dressing the flow.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
If the river rises, call it.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
- hydrographs
- catchments
- gauging
- floods
- low flow
- hydrology alerts
- flows
- the river authority
Sources for this job· O*NET 19-2043.00· ESCO/ISCO 2114
IS WORK OVER?
Technical writer
28%
#115 / 633
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641