Automation index
How much of a Cheesemaker’s job can AI already do?
A recipe and a pH come earlier. Setting, turning and signing the ageing do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Cheesemaker
22%
AI can already do 22% of this job.
#478 / 773
View rankingCheesemaker
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 |
|---|---|---|---|
Milk, pH and the day’s recipe.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Set, cut and the drain.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
Turn, salt and the ageing room.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Taste, the batch and the one that splits.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The co-op, the season and not selling too early.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Sign the ageing, and not forcing the pH.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- set curd
- drain whey
- turn cheeses
- ageing room
- milk pH
- salt
- taste batches
- cheese recipe
Sources for this job· O*NET 51-3092.00· ESCO/ISCO 7513
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