Automation index
How much of a Game developer’s job can AI already do?
A prototype comes earlier. It actually playing without leaving a frame at 8 do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Game developer
27%
AI can already do 27% of this job.
#153 / 763
View rankingGame 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 |
|---|---|---|---|
Prototype, the loop and the input.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Physics, the bug and the one that teleports.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Build, the platform and the one that will not ship.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Frame, 30 and not leaving it at 8.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the fun and not cutting what it feels.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it plays, and not leaving the frame at 8.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
- game prototypes
- game loop
- input
- builds
- frames
- physics bugs
- platforms
- write game code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514
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