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.
Most of this decline happened after 2021 — it is not the pandemic dip.
This line is counted by the Bureau of Labor Statistics — the one figure on this page that isn't a judgement of ours. Headcount moves on demand, offshoring, demographics and the business cycle, and automation is one term among several, often not the loudest.
So a falling line is not evidence that AI did it, and a rising one is not evidence that it won't. Both happen in this register: some occupations resist automation and shrink anyway, others are highly automatable and keep growing.
BLS projection, 2024–2034
-0.7% 78,000 → 77,500 on the projections basis
Exposed, and shrinking
Both signals point the same way: the tasks are largely automatable and the BLS projects -0.7% by 2034. This is the case where the score and the forecast agree, and it is the one worth taking seriously.
Different clocks. The score is what current AI could do to this work today. The projection is how many of these jobs will exist in 2034. Everything between the two — how fast employers actually adopt, whether demand grows in the meantime — is why they can point opposite ways without either being wrong.
~3,800 openings a year on average, including replacing people who leave.
Data MinerData EngineerDatabase TesterDatabase AnalystDatabase ManagerDatabase EngineerDatabase DeveloperDatabase ProgrammerDatabase SpecialistDatabase CoordinatorAdministrator (Admin)Data Recovery PlannerSecurity AdministratorData Storage SpecialistDatabase Design AnalystData Management AssociateData Security AdministratorDatabase Administrator (DBA)Database Computer ConsultantDatabase Software ConsultantInternet Database SpecialistData Administrator (Data Admin)Database Administration ManagerDatabase Security Administrator
Holding it up: judgment & accountability . Weakest point: liability shield .
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.
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.
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.
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.
The verdict above describes this occupation as a whole. Almost nobody does the typical version of a job — tick what's actually in your week and see how your own mix sits.
Your task mix speaks to task resistance (9/20 here) — how much of the day's work current AI already does. That is the dimension the boxes above are about.
It cannot move the other three. Liability shield (4/20) is whether the law requires a licensed human to sign. Trust premium (8/20) is whether buyers specifically pay for a person. Judgment and accountability (13/20) is whether the role exists to own consequential calls. Those are facts about the occupation's standing, not about which tasks are in your week — a paralegal who does only trial exhibits still holds no licence. Together they are 25 of this occupation's 38 points (66%).
Embodiment (4/20) is also a property of the work rather than the worker, but we don't tag individual tasks as physical or not, so the picker can't tell you anything about it. That's a limit of this tool, not a claim.
Did we get the list right? Tell us what's missing — the tasks are written from the outside, and you're reading this from the inside.
No occupation passed every test: close enough to database administrators on skills and subject matter, at least 10 points more resistant, no big jump in training, no new licence, no pay cut, and not shrinking on its own. That happens for 223 of the 654 occupations here that aren't SAFE, and it is worth stating plainly rather than leaving the section off.
The usual reason is that exposure travels with the skill profile. The jobs most similar to yours tend to be exposed for the same reasons yours is, so the near neighbours don't clear the gap — and the ones that do are a different kind of work, not a transfer of what you already know. Read that as a limit of this method, not a verdict that you're stuck: it only compares whole occupations, and it cannot see specialisation, industry, or anything you'd bring that isn't in a federal skill survey.
Here is that claim on your own job rather than in the abstract. These are the three occupations closest to this one by skill and subject matter — the places the work would most naturally transfer — with what the register scores them:
That is the whole problem in three lines. The nearest work is not meaningfully safer, so there is no move here that trades a similar skill set for a better verdict. This is not us running out of ideas — it is what the neighbourhood looks like.
The moves above are yours to make. This is the other half: what would have to change in the world for the occupation itself to score higher. None of it is in any one person's gift, but it is where the floor actually comes from. Scores here are not a one-way ratchet. Only two of the five dimensions — task resistance and embodiment — track what machines can do. The other three track law, what buyers will pay for, and who is answerable, and those move in both directions, often in response to the same pressure AI creates. If every lever below landed, this occupation would score around 53/100, still EXPOSED.
Task-mix compression: once managed services and code models absorb index tuning, backup scripting, patching and capacity reporting, what remains per company is schema/partition design against an unknown growth curve, cross-system data modeling, and live corruption recovery — work where the cost of a wrong call is unbounded and the context is proprietary. The occupation genuinely has two tiers, and headcount falls while the surviving role's resistance rises.
Named-individual accountability regimes for data systems: EU DORA (in force Jan 2025) requires financial entities to maintain a register of ICT assets with identified responsible parties and board-level accountability for resilience testing; UK/EU GDPR Art. 32 audits and SEC cyber-disclosure rules (Item 1.05) push firms to designate a specific person who attests that backup, retention and access-control configurations are as described. If audit standards harden that attestation into a signed, personally-defensible statement about database controls, the DBA/data-platform owner becomes the signer.
Post-incident regimes that assign the recovery decision to a named human: if breach-notification and operational-resilience rules (DORA severe-incident reporting, state breach laws) require a documented human decision on restore point, data-loss acceptance and failover under time pressure — i.e. the RPO/RTO call cannot be delegated to an autonomous system — the role's ownership of consequential ambiguous calls is formalized rather than assumed.
Healthcare and government contracting: HIPAA Security Rule updates (HHS Dec 2024 NPRM) proposing mandatory annual technical-control verification and asset inventories, and FedRAMP/CMMC assessment requirements, both push toward an identified individual certifying database access controls and encryption state to an assessor.
The limit. No plausible trust_premium route: buyers of database work are internal IT budgets and auditors, not consumers who can prefer a human — nobody pays extra to know a person wrote the partition key. Embodiment has no route; the residual on-prem/rack work is shrinking. Even with strong liability levers, the shield attaches to a shrinking number of senior seats, so the score can rise while the worker count falls.
| Washington-Arlington-Alexandria, DC-VA-MD-WV | 3,730 | $108,750 +4% |
| New York-Newark-Jersey City, NY-NJ | 3,630 | $121,550 +16% |
| Dallas-Fort Worth-Arlington, TX | 2,430 | $122,390 +17% |
| Los Angeles-Long Beach-Anaheim, CA | 2,280 | $112,540 +8% |
| Boston-Cambridge-Newton, MA-NH | 1,910 | $132,370 +27% |
| Chicago-Naperville-Elgin, IL-IN | 1,870 | $109,680 +5% |
| Atlanta-Sandy Springs-Roswell, GA | 1,780 | $110,950 +6% |
| Philadelphia-Camden-Wilmington, PA-NJ-DE-MD | 1,580 | $104,930 +0% |
| San Jose-Sunnyvale-Santa Clara, CA | 580 | $138,620 +32% |
| Seattle-Tacoma-Bellevue, WA | 1,010 | $133,180 +27% |
| Boston-Cambridge-Newton, MA-NH | 1,910 | $132,370 +27% |
We have no reported case of a named organisation automating this occupation. Not one deployment, not one announcement.
That is worth saying out loud next to a score of 38. The verdict above is about what the work exposes — what current AI could do to these tasks. It is not a claim that anyone has done it. For this occupation those two things have come apart completely: the capability argument is on this page, and the evidence column is empty.
Has AI actually changed your work? One tap, anonymous, and the running tally is public. Nothing else is asked of you.
Rather than check back: get the digest and we'll tell you what changed — or watch a single occupation from its own page.