Loading
Comparison · dataset August 2026

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

Data Analyst carries 6 points more AI exposure than Software Engineer.

Data Analyst sits at 73% time-weighted AI exposure against 67% for Software Engineer, a 6-point gap driven by the 39% of data analyst work time that current models can already substitute outright. Software Engineer holds a larger human-critical core — 20% of the role's time sits in work like "mentor junior engineers" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.

6PP GAP

Seven dimensions, side by side.

METRICDATA ANALYSTSOFTWARE ENGINEERDELTA
AI exposure73%67%6pp gap
Resilience score54/10069/10015pt gap
Substitutable work time39%32%Fully automatable today
Human-critical work time26%20%Models score poorly here
Median salary$86k$132k$46k apart
10-year growth23%17%Data Analyst
US workforce192k1.8MBLS OEWS
Task level

What actually creates the gap.

Data Analysts spend 39% 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 "sql query writing and optimization", graded at 91% and worth 16% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Data Analyst
MOST EXPOSED TASKS
  • SQL query writing and optimization91% · 16% time
  • Data cleaning and transformation88% · 12% time
  • Dashboard and report creation84% · 11% time
HUMAN-CRITICAL CORE
  • Stakeholder storytelling18% · 8% time
  • Cross-functional data strategy21% · 6% time
  • Business hypothesis formation28% · 12% 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 creative: Software Engineers score 61 there against 39 for Data Analysts, a 22-point spread. That is the gap you would actually have to close.

DIMENSIONDATA ANALYSTSOFTWARE ENGINEER
Creative3961
Judgement6141
Switching between them
LowDIFFICULTY

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

Data Analyst. It scores 73% time-weighted AI exposure against 67% for Software Engineer — a 6-point gap. 39% of data analyst work time is already fully substitutable by current models, versus 32% for Software Engineers.

Which pays more, Data Analyst or Software Engineer?

Software Engineer, by roughly $46k at the median ($132k versus $86k). 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 analyst switch to being a software engineer?

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 14 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 Analyst or Software Engineer?

Data Analyst, at 23% projected ten-year growth versus 17% — a 6-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.