Loading
Comparison · dataset August 2026

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

A 17-point gap separates these roles — Software Engineer is the more defensible seat.

Bookkeeper sits at 84% time-weighted AI exposure against 67% for Software Engineer, a 17-point gap driven by the 54% of bookkeeper 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 — Business & Finance and Computer & Math — so any move between them is a career change, not a lateral step.

17PP GAP

Seven dimensions, side by side.

METRICBOOKKEEPERSOFTWARE ENGINEERDELTA
AI exposure84%67%17pp gap
Resilience score30/10069/10039pt gap
Substitutable work time54%32%Fully automatable today
Human-critical work time18%20%Models score poorly here
Median salary$47k$132k$85k apart
10-year growth-5%17%Software Engineer
US workforce1.5M1.8MBLS OEWS
Task level

What actually creates the gap.

Bookkeepers 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 "categorize transactions", graded at 94% and worth 18% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

Bookkeeper
MOST EXPOSED TASKS
  • Categorize transactions94% · 18% time
  • Enter invoices and receipts93% · 12% time
  • Reconcile bank statements90% · 14% time
  • Generate recurring reports89% · 10% time
HUMAN-CRITICAL CORE
  • Handle sensitive payroll issues18% · 2% time
  • Liaise with accountants & auditors22% · 3% time
  • Advise owners on cash flow26% · 5% 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 creative: Software Engineers score 61 there against 12 for Bookkeepers, a 49-point spread. That is the gap you would actually have to close.

DIMENSIONBOOKKEEPERSOFTWARE ENGINEER
Creative1261
Cognitive5578
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 Bookkeeper or Software Engineer more at risk from AI?

Bookkeeper. It scores 84% time-weighted AI exposure against 67% for Software Engineer — a 17-point gap. 54% of bookkeeper work time is already fully substitutable by current models, versus 32% for Software Engineers.

Which pays more, Bookkeeper or Software Engineer?

Software Engineer, by roughly $85k at the median ($132k versus $47k). 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 bookkeeper 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, Bookkeeper or Software Engineer?

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