Data Engineer vs ML Engineer: which is more exposed to AI?
Data Engineer carries 9 points more AI exposure than ML Engineer.
Data Engineer sits at 65% time-weighted AI exposure against 56% for ML Engineer, a 9-point gap driven by the 44% of data engineer work time that current models can already substitute outright. ML Engineer holds a larger human-critical core — 36% of the role's time sits in work like "research direction and hypothesis setting" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.
Seven dimensions, side by side.
What actually creates the gap.
Data Engineers spend 44% of their time-weighted week on tasks a current model can produce end-to-end, against 28% for ML Engineers. The single largest contributor is "generate sql transformations", graded at 88% and worth 14% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.
- Generate SQL transformations88% · 14% time
- Write ETL pipeline code84% · 22% time
- Write data documentation78% · 8% time
- Stakeholder data requirements gathering16% · 8% time
- Architect data platform strategy22% · 10% time
- Data quality and contract management34% · 12% time
- Build data preprocessing pipelines82% · 12% time
- Write model training code78% · 16% time
- Research direction and hypothesis setting18% · 8% time
- Model architecture design28% · 16% time
- Production reliability and serving31% · 12% time
Both roles lean on cognitive, procedural, judgement — that is the part of your experience that travels intact. The real divide is creative: ML Engineers score 62 there against 44 for Data Engineers, an 18-point spread. That is the gap you would actually have to close.
| DIMENSION | DATA ENGINEER | ML ENGINEER |
|---|---|---|
| Creative | 44 | 62 |
| Judgement | 62 | 78 |
ML Engineer appears in our dataset as a mapped adjacent career for Data Engineers: the move lowers exposure by 9 points, landing at 56%. Switch difficulty reads low — capability profiles are 11 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is Data Engineer or ML Engineer more at risk from AI?
Data Engineer. It scores 65% time-weighted AI exposure against 56% for ML Engineer — a 9-point gap. 44% of data engineer work time is already fully substitutable by current models, versus 28% for ML Engineers.
Which pays more, Data Engineer or ML Engineer?
ML Engineer, by roughly $36k at the median ($158k versus $122k). Note that the higher-paying role here is also the less AI-exposed one, which matters if you are weighing pay against durability.
Can a data engineer switch to being a ml engineer?
ML Engineer appears in our dataset as a mapped adjacent career for Data Engineers: the move lowers exposure by 9 points, landing at 56%. Switch difficulty reads low — capability profiles are 11 points apart on average and both sit in the same family.
Which role is growing faster, Data Engineer or ML Engineer?
ML Engineer, at 28% projected ten-year growth versus 21% — a 7-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.