Automation index
How much of a Biochemist’s job can AI already do?
A protocol and a curve come earlier. An assay that says what it says does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Biochemist
24%
AI can already do 24% of this job.
#305 / 763
View rankingBiochemist
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, curves and analysis.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Bench, pipettes and assays.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Team, paper and not dressing a gel.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Quality, lots and documentation.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Rules, waste and safety.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not publishing a result that does not replicate.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Protocols, curves and analysis
- Bench, pipettes and assays
- Team, paper and not dressing a gel
- Quality, lots and documentation
- Rules, waste and safety
- bioquimico
- biochemist
Sources for this job· O*NET 19-1021.00· ESCO/ISCO 2131
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