Automation index
How much of a Product owner’s job can AI already do?
A backlog and a user story write fast. Telling engineering no, and a customer yes, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Product owner
27%
AI can already do 27% of this job.
#206 / 763
View rankingProduct owner
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 |
|---|---|---|---|
Write stories, criteria and backlog.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 50% | +11 |
Maps, roadmaps and release notes.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Refine with engineering and design.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Talk to users and stakeholders.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
Prioritise, cut scope and say no.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
Accept the increment and own the value.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Write stories, criteria and backlog
- Maps, roadmaps and release notes
- Refine with engineering and design
- Talk to users and stakeholders
- Prioritise, cut scope and say no
- Accept the increment and own the value
- product owner
- po agil
Sources for this job· O*NET 15-1199.09· ESCO/ISCO 2519
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