Loading
Comparison · dataset August 2026

Aerospace Engineer vs Research Scientist: which is more exposed to AI?

Research Scientist carries 5 points more AI exposure than Aerospace Engineer.

Research Scientist sits at 48% time-weighted AI exposure against 43% for Aerospace Engineer, a 5-point gap driven by the 34% of research scientist work time that current models can already substitute outright. Aerospace Engineer holds a larger human-critical core — 38% of the role's time sits in work like "own certification with regulators" that models score poorly on. The two sit in different families — Architecture & Engineering and Science & Research — so any move between them is a career change, not a lateral step.

5PP GAP

Seven dimensions, side by side.

METRICAEROSPACE ENGINEERRESEARCH SCIENTISTDELTA
AI exposure43%48%5pp gap
Resilience score70/10074/1004pt gap
Substitutable work time28%34%Fully automatable today
Human-critical work time38%52%Models score poorly here
Median salary$130k$124k$6k apart
10-year growth6%8%Research Scientist
US workforce65k148kBLS OEWS
Task level

What actually creates the gap.

Research Scientists spend 34% of their time-weighted week on tasks a current model can produce end-to-end, against 28% for Aerospace Engineers. The single largest contributor is "literature review and synthesis", graded at 88% and worth 18% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Aerospace Engineer
MOST EXPOSED TASKS
  • Draft technical documentation82% · 8% time
  • Compile test reports78% · 6% time
  • Generate routine CAD iterations72% · 8% time
  • Run parameter-sweep simulations70% · 6% time
HUMAN-CRITICAL CORE
  • Own certification with regulators12% · 10% time
  • Make safety-critical design decisions15% · 14% time
  • Lead design reviews20% · 5% time
Research Scientist
MOST EXPOSED TASKS
  • Literature review and synthesis88% · 18% time
  • Data analysis and statistical modelling82% · 16% time
HUMAN-CRITICAL CORE
  • Conduct laboratory experiments12% · 14% time
  • Peer review and scientific debate14% · 8% time
  • Interpret novel findings and implications18% · 12% time
What transfers

Both roles lean on cognitive, judgement, procedural — that is the part of your experience that travels intact. The real divide is manual: Research Scientists score 52 there against 22 for Aerospace Engineers, a 30-point spread. That is the gap you would actually have to close.

DIMENSIONAEROSPACE ENGINEERRESEARCH SCIENTIST
Manual2252
Creative5274
Social3854
Switching between them
ModerateDIFFICULTY

Research Scientist appears in our dataset as a mapped adjacent career for Aerospace Engineers: the move raises exposure by 5 points, landing at 48%. Switch difficulty reads moderate — capability profiles are 18 points apart on average.

Score your own exposure in 8 questions →

Common questions.

Is Aerospace Engineer or Research Scientist more at risk from AI?

Research Scientist. It scores 48% time-weighted AI exposure against 43% for Aerospace Engineer — a 5-point gap. 34% of research scientist work time is already fully substitutable by current models, versus 28% for Aerospace Engineers.

Which pays more, Aerospace Engineer or Research Scientist?

Aerospace Engineer, by roughly $6k at the median ($130k versus $124k). 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 aerospace engineer switch to being a research scientist?

Research Scientist appears in our dataset as a mapped adjacent career for Aerospace Engineers: the move raises exposure by 5 points, landing at 48%. Switch difficulty reads moderate — capability profiles are 18 points apart on average.

Which role is growing faster, Aerospace Engineer or Research Scientist?

Research Scientist, at 8% projected ten-year growth versus 6% — a 2-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.