Loading
Comparison · dataset August 2026

Data Scientist vs Software Engineer: which is more exposed to AI?

Effectively tied: 2 points separate Data Scientists from Software Engineers.

Data Scientist scores 65% time-weighted AI exposure and Software Engineer scores 67% — close enough that the headline number tells you almost nothing. The difference lives underneath it: Data Scientists lose the most ground on "clean and transform datasets" (88%), while for Software Engineers it is "write boilerplate & crud code" (92%). Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.

2PP GAP

Seven dimensions, side by side.

METRICDATA SCIENTISTSOFTWARE ENGINEERDELTA
AI exposure65%67%2pp gap
Resilience score64/10069/1005pt gap
Substitutable work time54%32%Fully automatable today
Human-critical work time24%20%Models score poorly here
Median salary$118k$132k$14k apart
10-year growth35%17%Data Scientist
US workforce202k1.8MBLS OEWS
Task level

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 32% for Software 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.

Data Scientist
MOST EXPOSED TASKS
  • 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
HUMAN-CRITICAL CORE
  • Communicate uncertainty to stakeholders14% · 8% time
  • Frame business and research questions18% · 10% time
  • Decide deployment and governance trade-offs22% · 6% time
Software Engineer
MOST EXPOSED TASKS
  • Write boilerplate & CRUD code92% · 14% time
  • Generate unit tests from specs88% · 8% time
  • Author documentation85% · 6% time
  • Translate code between languages81% · 4% time
HUMAN-CRITICAL CORE
  • Mentor junior engineers11% · 3% time
  • Negotiate scope with stakeholders14% · 5% time
  • Triage production incidents22% · 4% time
What transfers

Both roles lean on procedural, cognitive — that is the part of your experience that travels intact. The real divide is judgement: Data Scientists score 78 there against 41 for Software Engineers, a 37-point spread. That is the gap you would actually have to close.

DIMENSIONDATA SCIENTISTSOFTWARE ENGINEER
Judgement7841
Switching between them
LowDIFFICULTY

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 17 points apart on average and both sit in Computer & Math. In practice that means a move is plausible without retraining from scratch — the constraint is credentials and hiring convention, not capability.

Score your own exposure in 8 questions →

Common questions.

Is Data Scientist or Software Engineer more at risk from AI?

Software Engineer. It scores 67% time-weighted AI exposure against 65% for Data Scientist — a 2-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 54% for Data Scientists.

Which pays more, Data Scientist or Software Engineer?

Software Engineer, by roughly $14k at the median ($132k versus $118k). Note that the higher-paying role here is also the more AI-exposed one, which matters if you are weighing pay against durability.

Can a data scientist switch to being a software engineer?

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 17 points apart on average and both sit in Computer & Math. In practice that means a move is plausible without retraining from scratch — the constraint is credentials and hiring convention, not capability.

Which role is growing faster, Data Scientist or Software Engineer?

Data Scientist, at 35% projected ten-year growth versus 17% — an 18-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.

Career families
Computer & Math
Methodology
Scores are time-weighted across each role's canonical O*NET tasks, graded against current frontier-model capability. How we score.