Automation index
How much of a Water technician’s job can AI already do?
A network test comes earlier. Potable water without bursting the main do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Water technician
22%
AI can already do 22% of this job.
#381 / 633
View rankingWater technician
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 |
|---|---|---|---|
Network, test and the chlorine.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Leak, locate and the shut-off.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Tank, the level and the one that runs dry.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Notice, the neighbourhood and not leaving them dry.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The inspection, the figure and not dressing chlorine.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Potable, and the main whole.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
- water network
- chlorine
- leaks
- tanks
- tests
- shut-offs
- neighbourhoods
- mains
Sources for this job· O*NET 51-8031.00· ESCO/ISCO 3132
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