Automation index
How much of a 3D animator’s job can AI already do?
A blocking pass and a preview come earlier. Timing, weight, and a director buying it do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
3D animator
30%
AI can already do 30% of this job.
#45 / 763
View ranking3D animator
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 |
|---|---|---|---|
Blocking, layouts and previews.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 52% | +11.4 |
Simple rigs, cycles and technical cleanup.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 45% | +8.1 |
Spline, weight and character acting.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 20% | +3.2 |
Director and supervisor notes.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
Integrate with lighting, fx and editorial.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 18% | +2.5 |
Taste: which shot lives and which dies.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 30% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Blocking, layouts and previews
- Simple rigs, cycles and technical cleanup
- Spline, weight and character acting
- Director and supervisor notes
- Integrate with lighting, fx and editorial
- Taste: which shot lives and which dies
- animador 3d
- 3d animator
- motion graphics
Sources for this job· O*NET 27-1014.00· ESCO/ISCO 2166
IS WORK OVER?
Front-end developer
27%
#154 / 763
View rankingFront-end 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 |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.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
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513