Automation index
How much of a Data architect’s job can AI already do?
A lake diagram comes earlier. Data that can be used, and does not rot, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Data architect
28%
AI can already do 28% of this job.
#83 / 623
View rankingData architect
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 |
|---|---|---|---|
Models, lineage and the catalogue.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Pipelines, quality and the data contract.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The analyst who finds nothing and the mess.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Privacy, retention and the field you cannot keep.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The business, shadow IT and not building another lake.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it gets used, and not letting raw data rot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- model data
- lineage
- data catalogue
- data contracts
- pipeline quality
- retention
- data lakes
- privacy
Sources for this job· O*NET 15-1243.00· ESCO/ISCO 2511
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514