Loading
Comparison · dataset August 2026

Data Scientist vs QA / Test Engineer: which is more exposed to AI?

QA / Test Engineer carries 5 points more AI exposure than Data Scientist.

QA / Test Engineer sits at 70% time-weighted AI exposure against 65% for Data Scientist, a 5-point gap driven by the 34% of qa / test engineer work time that current models can already substitute outright. Data Scientist holds a larger human-critical core — 24% of the role's time sits in work like "communicate uncertainty to stakeholders" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.

5PP GAP

Seven dimensions, side by side.

METRICDATA SCIENTISTQA / TEST ENGINEERDELTA
AI exposure65%70%5pp gap
Resilience score64/10054/10010pt gap
Substitutable work time54%34%Fully automatable today
Human-critical work time24%40%Models score poorly here
Median salary$118k$92k$26k apart
10-year growth35%6%Data Scientist
US workforce202k224kBLS 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 34% for QA / Test 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
QA / Test Engineer
MOST EXPOSED TASKS
  • Generate unit and integration tests88% · 22% time
  • Write test documentation and plans82% · 12% time
HUMAN-CRITICAL CORE
  • Cross-team quality advocacy14% · 10% time
  • Test strategy and risk prioritisation22% · 12% time
  • Exploratory and edge-case testing28% · 18% time
What transfers

Both roles lean on procedural, cognitive, judgement — that is the part of your experience that travels intact. Beyond that, the two capability profiles are unusually close: no dimension separates them by more than 15 points, which is why the switch difficulty below reads the way it does.

Switching between them
LowDIFFICULTY

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 7 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 QA / Test Engineer more at risk from AI?

QA / Test Engineer. It scores 70% time-weighted AI exposure against 65% for Data Scientist — a 5-point gap. 34% of qa / test engineer work time is already fully substitutable by current models, versus 54% for Data Scientists.

Which pays more, Data Scientist or QA / Test Engineer?

Data Scientist, by roughly $26k at the median ($118k versus $92k). 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 scientist switch to being a qa / test engineer?

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 7 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 QA / Test Engineer?

Data Scientist, at 35% projected ten-year growth versus 6% — a 29-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.