Automation index
How much of a Inventory clerk’s job can AI already do?
A cycle count comes earlier. Matching what is there to what the system says do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Inventory clerk
28%
AI can already do 28% of this job.
#105 / 763
View rankingInventory clerk
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 |
|---|---|---|---|
Count, locations and the adjustment.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Floor, the gap and what is in the aisle.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Report, shrink and the reason.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 36% | +5.8 |
Audit, the auditor and not dressing it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The peak, the blind count and the stopped warehouse.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Match for real, and not adjusting blind.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
- cycle count
- adjust stock
- locations
- shrink
- blind count
- stock audit
- gaps
- variance reasons
Sources for this job· O*NET 43-5081.00· ESCO/ISCO 4321
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