Loading
Comparison · dataset August 2026

QA / Test Engineer vs Site Reliability Engineer: which is more exposed to AI?

A 27-point gap separates these roles — Site Reliability Engineer is the more defensible seat.

QA / Test Engineer sits at 70% time-weighted AI exposure against 43% for Site Reliability Engineer, a 27-point gap driven by the 34% of qa / test engineer work time that current models can already substitute outright. Site Reliability Engineer holds a larger human-critical core — 42% of the role's time sits in work like "mentor on-call engineers" that models score poorly on. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.

27PP GAP

Seven dimensions, side by side.

METRICQA / TEST ENGINEERSITE RELIABILITY ENGINEERDELTA
AI exposure70%43%27pp gap
Resilience score54/10072/10018pt gap
Substitutable work time34%23%Fully automatable today
Human-critical work time40%42%Models score poorly here
Median salary$92k$135k$43k apart
10-year growth6%18%Site Reliability Engineer
US workforce224k180kBLS OEWS
Task level

What actually creates the gap.

QA / Test Engineers spend 34% of their time-weighted week on tasks a current model can produce end-to-end, against 23% for Site Reliability Engineers. The single largest contributor is "generate unit and integration tests", graded at 88% and worth 22% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.

QA / Test Engineer
MOST EXPOSED TASKS
  • Generate unit and integration tests88% · 22% time
  • Write test documentation and plans82% · 12% time
HUMAN-CRITICAL CORE
  • Cross-team quality advocacy14% · 10% time
  • Test strategy and risk prioritisation22% · 12% time
  • Exploratory and edge-case testing28% · 18% time
Site Reliability Engineer
MOST EXPOSED TASKS
  • Write runbooks and documentation85% · 6% time
  • Draft infrastructure-as-code80% · 8% time
  • Generate postmortem first drafts78% · 4% time
  • Build monitoring dashboards72% · 5% time
HUMAN-CRITICAL CORE
  • Mentor on-call engineers12% · 4% time
  • Negotiate SLOs with product teams15% · 8% time
  • Command live incidents18% · 16% time
What transfers

Both roles lean on procedural, cognitive, judgement — that is the part of your experience that travels intact. Beyond that, the two capability profiles are unusually close: no dimension separates them by more than 15 points, which is why the switch difficulty below reads the way it does.

Switching between them
LowDIFFICULTY

Site Reliability Engineer appears in our dataset as a mapped adjacent career for QA / Test Engineers: the move lowers exposure by 27 points, landing at 43%. Switch difficulty reads low — capability profiles are 6 points apart on average and both sit in the same family.

Score your own exposure in 8 questions →

Common questions.

Is QA / Test Engineer or Site Reliability Engineer more at risk from AI?

QA / Test Engineer. It scores 70% time-weighted AI exposure against 43% for Site Reliability Engineer — a 27-point gap. 34% of qa / test engineer work time is already fully substitutable by current models, versus 23% for Site Reliability Engineers.

Which pays more, QA / Test Engineer or Site Reliability Engineer?

Site Reliability Engineer, by roughly $43k at the median ($135k versus $92k). 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 qa / test engineer switch to being a site reliability engineer?

Site Reliability Engineer appears in our dataset as a mapped adjacent career for QA / Test Engineers: the move lowers exposure by 27 points, landing at 43%. Switch difficulty reads low — capability profiles are 6 points apart on average and both sit in the same family.

Which role is growing faster, QA / Test Engineer or Site Reliability Engineer?

Site Reliability Engineer, at 18% projected ten-year growth versus 6% — a 12-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.

Career families
Computer & Math
Methodology
Scores are time-weighted across each role's canonical O*NET tasks, graded against current frontier-model capability. How we score.