Automation index
How much of a Astronomer’s job can AI already do?
A night of telescope time comes earlier. Reducing the data without selling the find early do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Astronomer
27%
AI can already do 27% of this job.
#139 / 763
View rankingAstronomer
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 |
|---|---|---|---|
Proposal, time and the instrument.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Observe, calibrate and the one that clouds over.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Reduce, the pipeline and the artefact.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Paper, the referee and not jumping.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The facility, the queue and not losing the night.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Reduce, and not selling the find early.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
- telescope time
- calibrate
- pipelines
- papers
- artefacts
- nights
- proposals
- instruments
Sources for this job· O*NET 19-2011.00· ESCO/ISCO 2111
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