Automation index
How much of a Wealth manager’s job can AI already do?
A model book comes earlier. Sitting with the client without selling them the house product do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Wealth manager
27%
AI can already do 27% of this job.
#171 / 763
View rankingWealth manager
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 |
|---|---|---|---|
Profile, IPS and the book.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Meeting, the fear and the one who wants it all on deposit.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Tax, succession and not leaving a hole.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Report, the market and not dressing the year.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The committee, the product and not pushing the house book.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Sit for real, and not selling the house product.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
- IPS
- wealth books
- succession
- wealth tax
- risk profiles
- client reports
- house products
- deposits
Sources for this job· O*NET 13-2052.00· ESCO/ISCO 2412
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