Loading
Comparison · dataset August 2026

Sales Representative vs Software Engineer: which is more exposed to AI?

Software Engineer carries 6 points more AI exposure than Sales Representative.

Software Engineer sits at 67% time-weighted AI exposure against 61% for Sales Representative, a 6-point gap driven by the 32% of software engineer work time that current models can already substitute outright. Sales Representative holds a larger human-critical core — 42% of the role's time sits in work like "build customer relationships" that models score poorly on. The two sit in different families — Business and Computer & Math — so any move between them is a career change, not a lateral step.

6PP GAP

Seven dimensions, side by side.

METRICSALES REPRESENTATIVESOFTWARE ENGINEERDELTA
AI exposure61%67%6pp gap
Resilience score60/10069/1009pt gap
Substitutable work time36%32%Fully automatable today
Human-critical work time42%20%Models score poorly here
Median salary$68k$132k$64k apart
10-year growth2%17%Software Engineer
US workforce1.5M1.8MBLS OEWS
Task level

What actually creates the gap.

Both roles hand a similar slice of the week to substitutable work — 36% for Sales Representatives, 32% for Software Engineers — but it is different work. Sales Representative exposure concentrates in "draft prospecting emails and sequences"; Software Engineer exposure concentrates in "write boilerplate & crud code". Two roles can share a score and face completely different disruption timelines.

Sales Representative
MOST EXPOSED TASKS
  • Draft prospecting emails and sequences91% · 14% time
  • Log CRM notes and update pipeline86% · 10% time
  • Research accounts and prospects82% · 12% time
HUMAN-CRITICAL CORE
  • Build customer relationships10% · 10% time
  • Close complex deals14% · 4% time
  • Handle objections and negotiate16% · 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 social: Sales Representatives score 92 there against 32 for Software Engineers, a 60-point spread. That is the gap you would actually have to close.

DIMENSIONSALES REPRESENTATIVESOFTWARE ENGINEER
Social9232
Judgement7641
Procedural6284
Switching between them
HighDIFFICULTY

Neither role lists the other as a mapped adjacent career, and the capability profiles sit 31 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.

Score your own exposure in 8 questions →

Common questions.

Is Sales Representative or Software Engineer more at risk from AI?

Software Engineer. It scores 67% time-weighted AI exposure against 61% for Sales Representative — a 6-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 36% for Sales Representatives.

Which pays more, Sales Representative or Software Engineer?

Software Engineer, by roughly $64k at the median ($132k versus $68k). Note that the higher-paying role here is also the more AI-exposed one, which matters if you are weighing pay against durability.

Can a sales representative switch to being a software engineer?

Neither role lists the other as a mapped adjacent career, and the capability profiles sit 31 points apart on average. Treat a move between them as a genuine career change with a retraining cost, not as a hedge against AI exposure.

Which role is growing faster, Sales Representative or Software Engineer?

Software Engineer, at 17% projected ten-year growth versus 2% — a 15-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.