Loading
Comparison · dataset August 2026

Receptionist vs Software Engineer: which is more exposed to AI?

Receptionist carries 8 points more AI exposure than Software Engineer.

Receptionist sits at 75% time-weighted AI exposure against 67% for Software Engineer, an 8-point gap driven by the 54% of receptionist work time that current models can already substitute outright. Software Engineer holds a larger human-critical core — 20% of the role's time sits in work like "mentor junior engineers" that models score poorly on. The two sit in different families — Office & Administrative and Computer & Math — so any move between them is a career change, not a lateral step.

8PP GAP

Seven dimensions, side by side.

METRICRECEPTIONISTSOFTWARE ENGINEERDELTA
AI exposure75%67%8pp gap
Resilience score35/10069/10034pt gap
Substitutable work time54%32%Fully automatable today
Human-critical work time24%20%Models score poorly here
Median salary$35k$132k$97k apart
10-year growth0%17%Software Engineer
US workforce1.0M1.8MBLS OEWS
Task level

What actually creates the gap.

Receptionists spend 54% 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 "schedule appointments", graded at 92% and worth 16% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Receptionist
MOST EXPOSED TASKS
  • Schedule appointments92% · 16% time
  • Manage email and messages90% · 10% time
  • Answer routine phone inquiries88% · 16% time
  • Update records and data entry86% · 8% time
HUMAN-CRITICAL CORE
  • Handle upset visitors18% · 5% time
  • Greet and assess visitors in person22% · 12% time
  • Manage building access protocols30% · 4% 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 — that is the part of your experience that travels intact. The real divide is creative: Software Engineers score 61 there against 10 for Receptionists, a 51-point spread. That is the gap you would actually have to close.

DIMENSIONRECEPTIONISTSOFTWARE ENGINEER
Creative1061
Cognitive3678
Social7032
Switching between them
HighDIFFICULTY

Neither role lists the other as a mapped adjacent career, and the capability profiles sit 32 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 Receptionist or Software Engineer more at risk from AI?

Receptionist. It scores 75% time-weighted AI exposure against 67% for Software Engineer — an 8-point gap. 54% of receptionist work time is already fully substitutable by current models, versus 32% for Software Engineers.

Which pays more, Receptionist or Software Engineer?

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

Neither role lists the other as a mapped adjacent career, and the capability profiles sit 32 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, Receptionist or Software Engineer?

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