Automation index
How much of a Chemist’s job can AI already do?
A protocol and a batch report come earlier. The smell of a reaction, and signing a certificate, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Chemist
26%
AI can already do 26% of this job.
#255 / 763
View rankingChemist
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 |
|---|---|---|---|
Protocols, calcs and safety sheets.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 45% | +9 |
Batch reports, charts and docs.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Synthesis, titration and sample handling.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 15% | +2.7 |
Read a strange result and repeat it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Plant safety and waste.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
Sign quality and talk to production.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 26% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Protocols, calcs and safety sheets
- Batch reports, charts and docs
- Synthesis, titration and sample handling
- Read a strange result and repeat it
- Plant safety and waste
- Sign quality and talk to production
- quimico
- chemist
- laboratorio quimico
Sources for this job· O*NET 19-2031.00· ESCO/ISCO 2113
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