Loading
Comparison · dataset August 2026

Data Scientist vs Quantitative Analyst: which is more exposed to AI?

Data Scientist and Quantitative Analyst score identically — for different reasons.

Data Scientist scores 65% time-weighted AI exposure and Quantitative Analyst scores 65% — 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 Quantitative Analysts it is "summarize research literature" (84%). The two sit in different families — Computer & Math and Business & Finance — so any move between them is a career change, not a lateral step.

TIED

Seven dimensions, side by side.

METRICDATA SCIENTISTQUANTITATIVE ANALYSTDELTA
AI exposure65%65%Tied
Resilience score64/10056/1008pt gap
Substitutable work time54%38%Fully automatable today
Human-critical work time24%32%Models score poorly here
Median salary$118k$145k$27k apart
10-year growth35%9%Data Scientist
US workforce202k55kBLS 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 38% for Quantitative Analysts. 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
Quantitative Analyst
MOST EXPOSED TASKS
  • Summarize research literature84% · 6% time
  • Implement models in code82% · 14% time
  • Run and document backtests80% · 10% time
  • Build data cleaning pipelines78% · 8% time
HUMAN-CRITICAL CORE
  • Decide when to pull a strategy15% · 8% time
  • Defend models to committees18% · 4% time
  • Judge model risk and regime shifts22% · 8% time
What transfers

Both roles lean on cognitive, judgement, procedural — that is the part of your experience that travels intact. The real divide is social: Data Scientists score 46 there against 30 for Quantitative Analysts, a 16-point spread. That is the gap you would actually have to close.

DIMENSIONDATA SCIENTISTQUANTITATIVE ANALYST
Social4630
Switching between them
LowDIFFICULTY

Data Scientist appears in our dataset as a mapped adjacent career for Quantitative Analysts: the move raises exposure by 0 points, landing at 65%. Switch difficulty reads low — capability profiles are 8 points apart on average.

Score your own exposure in 8 questions →

Common questions.

Is Data Scientist or Quantitative Analyst more at risk from AI?

Neither. Data Scientist and Quantitative Analyst both score 65% time-weighted AI exposure. The scores match, but the underlying tasks do not: Data Scientists are most exposed on "clean and transform datasets" (88%), Quantitative Analysts on "summarize research literature" (84%).

Which pays more, Data Scientist or Quantitative Analyst?

Quantitative Analyst, by roughly $27k at the median ($145k 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 quantitative analyst?

Data Scientist appears in our dataset as a mapped adjacent career for Quantitative Analysts: the move raises exposure by 0 points, landing at 65%. Switch difficulty reads low — capability profiles are 8 points apart on average.

Which role is growing faster, Data Scientist or Quantitative Analyst?

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

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