Loading
Comparison · dataset August 2026

Software Engineer vs Therapist / Counsellor: which is more exposed to AI?

48 points apart. These are not comparable risk profiles.

Software Engineer sits at 67% time-weighted AI exposure against 19% for Therapist / Counsellor, a 48-point gap driven by the 32% of software engineer work time that current models can already substitute outright. Therapist / Counsellor holds a larger human-critical core — 78% of the role's time sits in work like "crisis intervention" that models score poorly on. The two sit in different families — Computer & Math and Healthcare — so any move between them is a career change, not a lateral step.

48PP GAP

Seven dimensions, side by side.

METRICSOFTWARE ENGINEERTHERAPIST / COUNSELLORDELTA
AI exposure67%19%48pp gap
Resilience score69/10094/10025pt gap
Substitutable work time32%0%Fully automatable today
Human-critical work time20%78%Models score poorly here
Median salary$132k$58k$74k apart
10-year growth17%19%Therapist / Counsellor
US workforce1.8M912kBLS OEWS
Task level

What actually creates the gap.

Software Engineers spend 32% of their time-weighted week on tasks a current model can produce end-to-end, against 0% for Therapist / Counsellors. The single largest contributor is "write boilerplate & crud code", graded at 92% and worth 14% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

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
Therapist / Counsellor
MOST EXPOSED TASKS
    HUMAN-CRITICAL CORE
    • Crisis intervention4% · 14% time
    • Conduct therapy sessions6% · 38% time
    • Group therapy facilitation8% · 6% time
    What transfers

    Both roles lean on cognitive — that is the part of your experience that travels intact. The real divide is social: Therapist / Counsellors score 98 there against 32 for Software Engineers, a 66-point spread. That is the gap you would actually have to close.

    DIMENSIONSOFTWARE ENGINEERTHERAPIST / COUNSELLOR
    Social3298
    Judgement4192
    Procedural8444
    Switching between them
    HighDIFFICULTY

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

    Software Engineer. It scores 67% time-weighted AI exposure against 19% for Therapist / Counsellor — a 48-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 0% for Therapist / Counsellors.

    Which pays more, Software Engineer or Therapist / Counsellor?

    Software Engineer, by roughly $74k at the median ($132k versus $58k). 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 software engineer switch to being a therapist / counsellor?

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

    Therapist / Counsellor, at 19% projected ten-year growth versus 17% — 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.