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.
#387 / 633
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?
Mobile developer
28%
#92 / 633
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514