Loading
Comparison · dataset August 2026

Financial Analyst vs Quantitative Analyst: which is more exposed to AI?

A 17-point gap separates these roles — Quantitative Analyst is the more defensible seat.

Financial Analyst sits at 82% time-weighted AI exposure against 65% for Quantitative Analyst, a 17-point gap driven by the 62% of financial analyst work time that current models can already substitute outright. Quantitative Analyst holds a larger human-critical core — 32% of the role's time sits in work like "decide when to pull a strategy" that models score poorly on. Both roles sit inside Business & Finance, so the exposure difference reflects task design rather than a change of field.

17PP GAP

Seven dimensions, side by side.

METRICFINANCIAL ANALYSTQUANTITATIVE ANALYSTDELTA
AI exposure82%65%17pp gap
Resilience score40/10056/10016pt gap
Substitutable work time62%38%Fully automatable today
Human-critical work time21%32%Models score poorly here
Median salary$96k$145k$49k apart
10-year growth9%9%Financial Analyst
US workforce371k55kBLS OEWS
Task level

What actually creates the gap.

Financial Analysts spend 62% 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 "gather and clean market data", graded at 92% 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.

Financial Analyst
MOST EXPOSED TASKS
  • Gather and clean market data92% · 14% time
  • Build and update financial models88% · 22% time
  • Perform variance analysis84% · 10% time
  • Write investment research reports81% · 16% time
HUMAN-CRITICAL CORE
  • Manage client relationships12% · 7% time
  • Navigate regulatory negotiations19% · 4% time
  • Advise on capital allocation28% · 10% 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, procedural, judgement — that is the part of your experience that travels intact. The real divide is procedural: Financial Analysts score 91 there against 74 for Quantitative Analysts, a 17-point spread. That is the gap you would actually have to close.

DIMENSIONFINANCIAL ANALYSTQUANTITATIVE ANALYST
Procedural9174
Judgement6278
Switching between them
LowDIFFICULTY

Quantitative Analyst appears in our dataset as a mapped adjacent career for Financial Analysts: the move lowers exposure by 17 points, landing at 65%. Switch difficulty reads low — capability profiles are 11 points apart on average and both sit in the same family.

Score your own exposure in 8 questions →

Common questions.

Is Financial Analyst or Quantitative Analyst more at risk from AI?

Financial Analyst. It scores 82% time-weighted AI exposure against 65% for Quantitative Analyst — a 17-point gap. 62% of financial analyst work time is already fully substitutable by current models, versus 38% for Quantitative Analysts.

Which pays more, Financial Analyst or Quantitative Analyst?

Quantitative Analyst, by roughly $49k at the median ($145k versus $96k). 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 financial analyst switch to being a quantitative analyst?

Quantitative Analyst appears in our dataset as a mapped adjacent career for Financial Analysts: the move lowers exposure by 17 points, landing at 65%. Switch difficulty reads low — capability profiles are 11 points apart on average and both sit in the same family.

Which role is growing faster, Financial Analyst or Quantitative Analyst?

Both are projected at 9% over ten years (faster than avg).

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