IS WORK OVER?

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

Hydrologist

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
Hydrograph, catchment and the model.
Estimate

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

16%40%+6.4
Field, gauging and the one that does not read.
Estimate

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

18%14%+2.5
Flood, the alert and not delaying.
Estimate

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

16%28%+4.5
Low flow, irrigation and the clash.
Estimate

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

16%22%+3.5
The authority, the figure and not dressing the flow.
Estimate

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

18%18%+3.2
If the river rises, call it.
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

  • hydrographs
  • catchments
  • gauging
  • floods
  • low flow
  • hydrology alerts
  • flows
  • the river authority

Sources for this job· O*NET 19-2043.00· ESCO/ISCO 2114

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. 392Geriatrician22%
  2. 393Nature guide22%
  3. 394Ice-cream maker22%
  4. 396Agronomist22%
  5. 397Control engineer22%
  6. 398Corrosion engineer22%