Automation index
How much of a Composer’s job can AI already do?
A mock-up and a part come earlier. Something that sounds and can be played does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Composer
21%
AI can already do 21% of this job.
#411 / 633
View rankingComposer
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 |
|---|---|---|---|
Mock-ups, parts and a first arrangement.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Write, orchestrate and review with players.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
Director, producer and opening deadlines.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Rights, publishers and versions.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Studio, libraries and delivery.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not delivering a score that cannot be played.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 21% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Mock-ups, parts and a first arrangement
- Write, orchestrate and review with players
- Director, producer and opening deadlines
- Rights, publishers and versions
- Studio, libraries and delivery
- compositor
- composer
Sources for this job· O*NET 27-2041.00· ESCO/ISCO 2652
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