Data Engineer vs Data Scientist: which is more exposed to AI?
Data Engineer and Data Scientist score identically — for different reasons.
Data Engineer scores 65% time-weighted AI exposure and Data Scientist scores 65% — close enough that the headline number tells you almost nothing. The difference lives underneath it: Data Engineers lose the most ground on "generate sql transformations" (88%), while for Data Scientists it is "clean and transform datasets" (88%). 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 Scientists spend 54% of their time-weighted week on tasks a current model can produce end-to-end, against 44% for Data Engineers. The single largest contributor is "clean and transform datasets", 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
- Clean and transform datasets88% · 14% time
- Write analysis code and notebooks84% · 16% time
- Generate charts and exploratory summaries82% · 10% time
- Build baseline predictive models78% · 14% time
- Communicate uncertainty to stakeholders14% · 8% time
- Frame business and research questions18% · 10% time
- Decide deployment and governance trade-offs22% · 6% time
Both roles lean on procedural, cognitive, judgement — that is the part of your experience that travels intact. The real divide is judgement: Data Scientists score 78 there against 62 for Data Engineers, a 16-point spread. That is the gap you would actually have to close.
| DIMENSION | DATA ENGINEER | DATA SCIENTIST |
|---|---|---|
| Judgement | 62 | 78 |
Data Engineer appears in our dataset as a mapped adjacent career for Data Scientists: the move raises exposure by 0 points, landing at 65%. Switch difficulty reads low — capability profiles are 9 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is Data Engineer or Data Scientist more at risk from AI?
Neither. Data Engineer and Data Scientist both score 65% time-weighted AI exposure. The scores match, but the underlying tasks do not: Data Engineers are most exposed on "generate sql transformations" (88%), Data Scientists on "clean and transform datasets" (88%).
Which pays more, Data Engineer or Data Scientist?
Data Engineer, by roughly $4k at the median ($122k versus $118k). 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 data scientist?
Data Engineer appears in our dataset as a mapped adjacent career for Data Scientists: the move raises exposure by 0 points, landing at 65%. Switch difficulty reads low — capability profiles are 9 points apart on average and both sit in the same family.
Which role is growing faster, Data Engineer or Data Scientist?
Data Scientist, at 35% projected ten-year growth versus 21% — a 14-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.