Loading
Comparison · dataset August 2026

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

Effectively tied: 1 point separates Business Analysts from Software Engineers.

Business Analyst scores 68% time-weighted AI exposure and Software Engineer scores 67% — close enough that the headline number tells you almost nothing. The difference lives underneath it: Business Analysts lose the most ground on "create dashboards and business reports" (84%), while for Software Engineers it is "write boilerplate & crud code" (92%). The two sit in different families — Business and Computer & Math — so any move between them is a career change, not a lateral step.

1PP GAP

Seven dimensions, side by side.

METRICBUSINESS ANALYSTSOFTWARE ENGINEERDELTA
AI exposure68%67%1pp gap
Resilience score56/10069/10013pt gap
Substitutable work time56%32%Fully automatable today
Human-critical work time44%20%Models score poorly here
Median salary$88k$132k$44k apart
10-year growth9%17%Software Engineer
US workforce942k1.8MBLS OEWS
Task level

What actually creates the gap.

Business Analysts spend 56% 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 "create dashboards and business reports", graded at 84% and worth 10% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Business Analyst
MOST EXPOSED TASKS
  • Create dashboards and business reports84% · 10% time
  • Write user stories and acceptance criteria82% · 14% time
  • Gather and document business requirements78% · 20% time
  • Data analysis and process mapping76% · 12% time
HUMAN-CRITICAL CORE
  • Requirements negotiation and prioritisation14% · 14% time
  • Change management and communication16% · 12% time
  • Stakeholder workshops and elicitation18% · 18% 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 social: Business Analysts score 74 there against 32 for Software Engineers, a 42-point spread. That is the gap you would actually have to close.

DIMENSIONBUSINESS ANALYSTSOFTWARE ENGINEER
Social7432
Judgement7641
Switching between them
ModerateDIFFICULTY

Neither role lists the other as a mapped adjacent career. With 23 points of average separation across capability dimensions, a move is realistic but not free: expect to deliberately rebuild the dimensions listed above rather than assume they carry.

Score your own exposure in 8 questions →

Common questions.

Is Business Analyst or Software Engineer more at risk from AI?

Business Analyst. It scores 68% time-weighted AI exposure against 67% for Software Engineer — a 1-point gap. 56% of business analyst work time is already fully substitutable by current models, versus 32% for Software Engineers.

Which pays more, Business Analyst or Software Engineer?

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

Neither role lists the other as a mapped adjacent career. With 23 points of average separation across capability dimensions, a move is realistic but not free: expect to deliberately rebuild the dimensions listed above rather than assume they carry.

Which role is growing faster, Business Analyst or Software Engineer?

Software Engineer, at 17% projected ten-year growth versus 9% — an 8-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.