Automation index
How much of a Backend developer’s job can AI already do?
An endpoint comes earlier. It taking the spike without leaving the key in the code do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Backend developer
27%
AI can already do 27% of this job.
#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
IS WORK OVER?
Game developer
27%
#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