Automation index
How much of a Costume designer’s job can AI already do?
A costume sketch comes earlier. A costume you can act in that does not split on the third night do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Costume designer
22%
AI can already do 22% of this job.
#387 / 763
View rankingCostume designer
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 |
|---|---|---|---|
The reading, sketch and the palette.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Shop, fitting and the one you cannot sit in.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Rehearsal, quick change and the one that catches.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Budget, dyes and the one that is late.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Direction, the ego and not dressing against the text.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
That you can act, and not splitting on the third.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
- costume sketches
- costume fittings
- quick changes
- palette
- wardrobe shop
- dyes
- rehearsals
- costume budget
Sources for this job· O*NET 27-1022.00· ESCO/ISCO 2163
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