Loading
Comparison · dataset August 2026

Aerospace Engineer vs Urban Planner: which is more exposed to AI?

Urban Planner carries 5 points more AI exposure than Aerospace Engineer.

Urban Planner sits at 48% time-weighted AI exposure against 43% for Aerospace Engineer, a 5-point gap driven by the 30% of urban planner 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. Both roles sit inside Architecture & Engineering, so the exposure difference reflects task design rather than a change of field.

5PP GAP

Seven dimensions, side by side.

METRICAEROSPACE ENGINEERURBAN PLANNERDELTA
AI exposure43%48%5pp gap
Resilience score70/10072/1002pt gap
Substitutable work time28%30%Fully automatable today
Human-critical work time38%58%Models score poorly here
Median salary$130k$82k$48k apart
10-year growth6%4%Aerospace Engineer
US workforce65k42kBLS OEWS
Task level

What actually creates the gap.

Both roles hand a similar slice of the week to substitutable work — 28% for Aerospace Engineers, 30% for Urban Planners — but it is different work. Aerospace Engineer exposure concentrates in "draft technical documentation"; Urban Planner exposure concentrates in "analyse land use and demographic data". Two roles can share a score and face completely different disruption timelines.

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
Urban Planner
MOST EXPOSED TASKS
  • Analyse land use and demographic data84% · 16% time
  • Write planning reports and environmental assessments76% · 14% time
HUMAN-CRITICAL CORE
  • Community engagement and public meetings12% · 22% time
  • Interagency and political coordination14% · 12% time
  • Policy development and zoning decisions18% · 18% 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: Urban Planners score 78 there against 38 for Aerospace Engineers, a 40-point spread. That is the gap you would actually have to close.

DIMENSIONAEROSPACE ENGINEERURBAN PLANNER
Social3878
Switching between them
LowDIFFICULTY

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 18 points apart on average and both sit in Architecture & Engineering. 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 Aerospace Engineer or Urban Planner more at risk from AI?

Urban Planner. It scores 48% time-weighted AI exposure against 43% for Aerospace Engineer — a 5-point gap. 30% of urban planner work time is already fully substitutable by current models, versus 28% for Aerospace Engineers.

Which pays more, Aerospace Engineer or Urban Planner?

Aerospace Engineer, by roughly $48k at the median ($130k versus $82k). 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 urban planner?

Neither role lists the other as a mapped adjacent career, but the capability profiles are only 18 points apart on average and both sit in Architecture & Engineering. 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, Aerospace Engineer or Urban Planner?

Aerospace Engineer, at 6% projected ten-year growth versus 4% — 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.