← Risk register SOC 15-1242 · reviewed 2026-08-11

Database Administrators

69,990 US workers · median $104,620/yr · Tech

EXPOSED

The bread-and-butter DBA workload — writing and tuning SQL, building indexes, scripting backups, provisioning instances, patching, generating capacity reports — is exactly what managed cloud services (RDS, Aurora, Autonomous Database) and code-generating models already handle at usable quality. What resists is the accountable side: designing schemas and partitioning strategies for a specific business's growth curve, owning the recovery when a production database corrupts at 2am, and defending data access controls to auditors. The occupation is not disappearing so much as compressing toward fewer, more senior data-platform owners per company.

10-year outlook: Headcount keeps drifting down as managed cloud databases absorb routine administration, while the remaining roles pay more and look increasingly like data-platform engineering with on-call accountability.

Score — 38/100 resistance

Five dimensions, 0–20 each, summed. Higher means more protected. The arithmetic is shown so you can check it: 9 + 4 + 4 + 8 + 13 = 38.

Task resistance 9/20

Mixed — a routine tier and a judgment tier. Index recommendations, execution-plan tuning, backup scripting, replication setup, and version upgrades are all now either autopiloted by RDS/Autonomous or one prompt away, which caps this at 9 — the remainder that holds is capacity modelling against a specific business's growth curve and untangling a multi-terabyte corruption with no clean restore point.

Embodiment 4/20

Fully desk- and screen-based. A 4 reflects the residue of racked on-prem servers — walking a datacentre to reseat a failed disk array or attend a cutover window — but the overwhelming majority of the job is SSH, a console, and a ticket queue that can be worked from anywhere.

Liability shield 4/20

No licence, no signature requirement. No state licence gates database administration; Oracle OCP, Microsoft or AWS certifications get you shortlisted but no regulator can pull them, and when a breach happens it is the company that answers under HIPAA or SOX while the DBA answers to their manager.

Trust premium 8/20

Some relationship component. An 8 recognises that developers escalate to the DBA they trust with prod credentials and that auditors want a familiar name walking them through access controls, but the artifact you deliver — a schema, a grant, a restored table — is judged on whether it works, not on who produced it.

Judgment & accountability 13/20

Meaningful discretion. 13 is earned in the 2am window: deciding whether to fail over, roll back a migration mid-flight, or accept data loss to restore service is a call with no runbook and real revenue attached, and schema and partitioning decisions bind the application for years — it stops short of 14+ because most weeks are change-control tickets under an approved process.

Confidence: high · reviewed 2026-08-11 · how scoring works

Tasks already automatable

What survives

Active moats: judgment, trust

How to future-proof this job

Field report — do you do this job?

Has AI actually changed your work?

Self-reported and unverified — a sentiment signal, not a survey. One response per person per occupation; you can change your answer.

From people who do this job

Nobody has filed one yet. If you do this work, you know things the rubric can't see.

What has actually changed in your work?

Concrete beats general: a tool that arrived, a task that moved, a headcount decision you watched happen. Don't include anything that identifies you or your employer if that would put you at risk.