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 / 733
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?
Reliability engineer
27%
#175 / 733
View rankingReliability engineer
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 |
|---|---|---|---|
Data, MTBF and the Pareto.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Failure, the cause and not patching twice.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Spare, the critical and not hiding it.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
RCM, the plan and the one that is not done.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Production, the rush and not running the tired one.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not drop at three, and not hiding the spare.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
- MTBF
- Pareto
- root causes
- critical spares
- RCM
- failures
- maintenance plans
- not patch twice
Sources for this job· O*NET 17-2112.00· ESCO/ISCO 2141