Database administration is one of the few IT disciplines where the best work is invisible. When a DBA is doing their job well, databases are fast, backups run cleanly, and no one calls. The CV problem this creates is significant: years of disciplined, high-responsibility database management can look thin on paper if the candidate only lists maintenance tasks rather than the scale they managed, the performance problems they solved, and the failures they prevented. The most common DBA CV failure is exactly this — a list of platforms and tasks ("SQL Server administration, backup management, performance monitoring") with no database size, no instance count, no uptime percentage, and no evidence that the work had any measurable impact. The second failure is platform staleness: on-premise-only SQL Server or Oracle experience, with no cloud database skills, is an increasing filter for roles at organisations that have moved or are moving their database estate to AWS RDS, Azure SQL, or managed PostgreSQL. This guide covers the structure, keywords, and bullet patterns that make a DBA CV legible and competitive in 2026.

What Database Administrator Job Descriptions Require in 2026

DBA JDs split by platform more sharply than most IT roles — SQL Server, Oracle, and PostgreSQL/MySQL are distinct hiring markets with different certification tracks and tooling. Identify your primary platform and lead with it.

Requirements across the majority of DBA JDs in 2026:

  • Primary RDBMS at production depth — SQL Server (2016–2022) for Microsoft-stack organisations; Oracle Database (12c–21c) for financial services, utilities, and enterprise applications; PostgreSQL for tech companies and modern stacks; MySQL/MariaDB for web-scale and SMB. JDs name the platform and version explicitly. Your headline should match.
  • High availability and disaster recovery — SQL Server Always On Availability Groups, Oracle Data Guard/RAC, or PostgreSQL streaming replication. Production DBA roles own the HA layer. Backup-only DBAs without HA experience are filtered for senior roles. RTO and RPO awareness is expected.
  • Performance tuning — query optimisation, execution plan analysis, index management, wait statistics analysis, and statistics maintenance. This is the primary technical differentiator between DBAs. If you have measurable performance wins, they belong in your bullets.
  • Backup and recovery — automated backup scheduling, restoration testing, point-in-time recovery, and documented recovery procedures. "Tested backups" is meaningless without frequency and success rate. "Maintained weekly full and daily differential backup schedule for 18TB estate with monthly restoration tests achieving verified RTO of 90 minutes" is evidence.
  • Cloud database — AWS RDS, Amazon Aurora, Azure SQL Database, Azure SQL Managed Instance, or GCP Cloud SQL. Mid-level and above JDs increasingly list cloud database experience as required rather than preferred. Database migration experience (on-premise to cloud) is in high demand.
  • Security and compliance — Transparent Data Encryption (TDE), data masking, role-based access control, audit logging, and GDPR/data residency compliance. Senior DBA JDs consistently list security ownership.

Database administrator salaries in 2026: £45K–£80K UK; $85K–$130K US. Senior DBAs with cloud migration and performance tuning depth reach £95K/$150K.

ATS Keywords for a Database Administrator Resume

DBA ATS filtering is platform-specific. "SQL Server" and "Oracle" as exact strings, alongside specific version numbers and tooling names, matter more than generic "database experience."

Essential ATS terms for a database administrator resume:

  • Title variants: Database Administrator, DBA, SQL Server DBA, Oracle DBA, PostgreSQL DBA, Senior Database Administrator, Cloud DBA
  • SQL Server: Microsoft SQL Server, T-SQL, SSMS, SSIS, SSRS, Always On, SQL Server Agent, DBCC, linked servers
  • Oracle: Oracle Database, PL/SQL, Oracle RAC, Oracle RMAN, Data Guard, Oracle DBA, ASM, Oracle 19c
  • Open source: PostgreSQL, MySQL, MariaDB, MongoDB, NoSQL, pgAdmin, replication
  • Cloud: AWS RDS, Amazon Aurora, Azure SQL Database, Azure SQL Managed Instance, GCP Cloud SQL, AWS DMS, database migration
  • HA and DR: Always On Availability Groups, failover clustering, log shipping, database mirroring, backup and recovery, RTO, RPO, point-in-time recovery
  • Performance: query optimisation, execution plans, index management, wait statistics, performance tuning, query store
  • Security: Transparent Data Encryption, TDE, data masking, RBAC, audit logging, GDPR, data governance
  • Long-tail phrases: database administrator resume examples, how to write a DBA resume, SQL Server DBA cv, Oracle DBA resume, database administrator skills

Placement: Your primary platform (SQL Server / Oracle / PostgreSQL) in the headline alongside your most distinctive skill (Always On, performance tuning, cloud migration). Cloud database platforms in your Skills section — even if secondary — signal currency with the market direction.

Database Administrator CV Structure and Bullets That Surface the Scale

Section order:

  1. Headline — "Database Administrator | SQL Server 2016–2022 · Always On · T-SQL · AWS RDS · Performance Tuning"
  2. Certifications — Microsoft Certified: Azure Database Administrator Associate, OCP, AWS Database Specialty; near the top
  3. Skills — Database Platforms / High Availability & DR / Cloud Databases / Performance & Tuning / Security & Compliance
  4. Experience — 4–6 bullets per role; database size, instance count, uptime, and tuning results are the primary evidence
  5. Education — CS, information systems, or mathematics degree; bottom

Two pages for 4+ years; one to two pages for under 4. Every bullet should state the scale of the database estate you managed and the outcome of your work.

Three elements make a DBA bullet convincing: the platform and scale (instance count, database size), the action or responsibility, and the outcome (uptime, performance improvement, cost, or incident prevented). Three examples:

  • Managed 34 SQL Server instances (2016–2022) hosting 280 databases totalling 18TB across 3 environments — maintained 99.99% availability on production instances using Always On Availability Groups with automatic failover; zero data loss events across 3 years of database ownership
  • Reduced average nightly batch job runtime from 4.2 hours to 38 minutes by rewriting 12 long-running T-SQL queries — identified missing indexes and stale statistics as root causes through execution plan analysis; batch SLA restored after 6 months of recurring breaches that had delayed morning reporting for 400 finance users
  • Migrated 6 on-premise SQL Server databases (combined 4.2TB) to AWS RDS Multi-AZ using AWS DMS — executed with schema validation, data integrity checks, and a 2-hour cutover window achieving zero unplanned downtime; completed 2 weeks ahead of data centre exit deadline

DBA interviews test two things: incident response ("production database is responding slowly at 9am on a Monday — walk me through your diagnostic process") and design ("we need to design a HA solution for this database — what's your recommendation?"). Your CV's uptime and performance evidence determines the scale of scenario you receive and the seniority of the technical discussion.

Three Database Administrator CV Mistakes That Leave Evidence on the Table

Database size and instance count never mentioned. A DBA managing 3 databases totalling 200GB and a DBA managing 300 databases totalling 50TB write identically vague bullets if neither mentions scale. Database size, instance count, and environment count (dev/test/prod) are the primary variables that determine the complexity of the DBA role — and therefore the seniority of the position the CV is competitive for. Add these numbers wherever they exist. They are not sensitive; they are the evidence the recruiter needs to place you correctly.

"Maintained backups" without RTO or RPO. Every DBA says they manage backups. The question no one answers is: what happens when you need to restore? What is the recovery time objective, and have you tested it? "Maintained SQL Server backup schedule and performed quarterly restoration tests verifying RTO of 2 hours for production databases" is evidence of backup discipline. "Maintained database backups" is a task description that tells the recruiter nothing they can evaluate. Add the RPO (how much data would be lost), the RTO (how long to recover), and whether you have tested both — restoration testing is neglected by most DBAs and it is the first thing a thorough interviewer asks about.

No performance tuning evidence. Performance tuning is the primary value-add of a skilled DBA over an accidental one. If you have ever taken a slow query from minutes to seconds, identified an index fragmentation problem before users reported it, or resolved a blocking chain that was causing timeouts — that evidence belongs on your CV. Most DBA CVs list "performance monitoring" as a skill and provide zero evidence of a performance problem actually solved. A single specific tuning win — with the before and after query time, the root cause, and the business impact (users affected, SLA restored) — differentiates your CV from every other applicant who claims to do performance work.

If you are applying to database administrator or cloud DBA roles and want your CV rebuilt around the specific SQL Server, Oracle, or PostgreSQL requirements in a target job description, Resumegpt generates your database administrator CV from your work history in under 60 seconds — database scale surfaced, performance wins evidenced, ATS-optimised, and exported as a PDF ready to submit.