Automation index
How much of a Climatologist’s job can AI already do?
A series comes earlier. Attributing the change without selling the easy headline do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Climatologist
27%
AI can already do 27% of this job.
#145 / 763
View rankingClimatologist
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 |
|---|---|---|---|
Series, homogenise and the gap.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Models, scenarios and the uncertainty.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Report, the headline and not selling the easy one.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Field, the station and the one that moves.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The politician, the figure and not staying quiet.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Attribute, and not selling the headline.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
- climate series
- homogenise
- scenarios
- uncertainty
- headlines
- stations
- climate reports
- attribution
Sources for this job· O*NET 19-2021.00· ESCO/ISCO 2112
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