IS WORK OVER?

Automation index

How much of a Meteorologist’s job can AI already do?

A model and a map come earlier. Saying whether a village should evacuate does not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Meteorologist

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
Models, maps and a first forecast.
Estimate

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

18%48%+8.6
Observation, sondes and satellite.
Estimate

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

16%28%+4.5
Warnings, civil protection and media.
Estimate

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

16%22%+3.5
Shift, uncertainty and not over-scaring.
Estimate

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

16%18%+2.9
Verification, archives and research.
Estimate

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

18%16%+2.9
Not sitting on a warning that saves someone.
Estimate

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

16%14%+2.2
Total100%25%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • Models, maps and a first forecast
  • Observation, sondes and satellite
  • Warnings, civil protection and media
  • Shift, uncertainty and not over-scaring
  • Verification, archives and research
  • meteorologo

Sources for this job· O*NET 19-2021.00· ESCO/ISCO 2112

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. 289Brewer25%
  2. 290Tool and die maker25%
  3. 291Auto mechanic25%
  4. 293Motion designer25%
  5. 294Education specialist25%
  6. 295Political scientist25%