Automation index
How much of a Pharmacy technician’s job can AI already do?
A count and an order come earlier. Dispensing without mixing up the blister does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Pharmacy technician
22%
AI can already do 22% of this job.
#494 / 773
View rankingPharmacy technician
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 |
|---|---|---|---|
Counts, orders and expiry dates.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Dispense, prepare and label.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Counter service and basic dosing.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Compounds, repack and records.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Pharmacy on-call and emergency stock.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Not mixing up a drug or a patient.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 14% | +2 |
| Total | 100% | 23% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Counts, orders and expiry dates
- Dispense, prepare and label
- Counter service and basic dosing
- Compounds, repack and records
- Pharmacy on-call and emergency stock
- Not mixing up a drug or a patient
- tecnico de farmacia
- auxiliar de farmacia
- pharmacy technician
Sources for this job· O*NET 29-2052.00· ESCO/ISCO 3213
IS WORK OVER?
Backend developer
27%
#153 / 773
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