Automation index
How much of a Instructional designer’s job can AI already do?
A course storyboard comes earlier. Someone learning without leaving a pretty empty video do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Instructional designer
27%
AI can already do 27% of this job.
#162 / 763
View rankingInstructional 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 |
|---|---|---|---|
Aim, the storyboard and the module.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Pilot, the learner and what is not understood.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Activity, the feedback and not putting a silly test.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
LMS, the figure and not inflating completion.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The client, the deadline and not cutting the practice.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That they learn, and not leaving the empty video.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
- course storyboard
- modules
- learner pilot
- activities
- LMS
- completion
- feedback
- not a silly test
Sources for this job· O*NET 25-9031.00· ESCO/ISCO 2351
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