Database Administrator resume example

• Entry level

  Junior database administrator with two years of SQL Server support and one year as a report developer. Runs nightly backup checks, monthly restore tests and index maintenance for 25 instances, and writes T-SQL and PowerShell scripts for routine tasks. Holds the Azure Database Administrator Associate credential and wants to grow on an operations team running production databases.

• Mid level

  Database administrator with six years supporting Oracle 19c and PostgreSQL for medical billing and claims systems. Looks after 60 instances and 22 TB, set up Data Guard standby databases with tested failover, and finished two major version upgrades with under 30 minutes of downtime each. Tunes slow queries with AWR and pg_stat_statements and supports HIPAA audits.

• Senior

  Lead database administrator with fifteen years running Oracle, SQL Server and PostgreSQL estates for financial services. Owns 200 instances and 80 TB across two data centers and AWS, designed the high availability standard used company-wide and led the move of 45 databases to Amazon RDS. Mentors four DBAs and works with security on audit readiness.

• Writing "managed databases" with no scale

  Fix: Give the number of instances, total data size, peak load and the uptime target you supported. "Supported 120 SQL Server instances, 18 TB, with a 99.9% availability target" tells a team immediately whether you have run an estate like theirs. Without numbers, a reviewer cannot tell a single test server from a production fleet.

• Never mentioning a restore

  Fix: Backups that were never restored prove little. Include restore drills, real recoveries after a failure or bad deployment, and the time they took. If you wrote the recovery runbook or automated restore verification, say so. Teams hiring a DBA worry most about the day data is lost, so show you have handled it.

• Hiding security and compliance work

  Fix: DBAs often own encryption at rest, access reviews, auditing and patching. Mention Transparent Data Encryption, role-based access, removal of shared logins and the audits you supported, such as SOX, PCI DSS or HIPAA reviews. Say how many findings you closed. This matters a great deal at banks, hospitals and government agencies.

• Describing tuning without before and after

  Fix: "Optimized queries" is too vague. Name the problem and the measured change: "rewrote a reporting query and added a covering index, cutting run time from 14 minutes to 40 seconds." Mention the tools behind it, such as execution plans, AWR reports, Query Store or pg_stat_statements, so a reviewer sees how you diagnose.

Match these against the job posting you are applying to: the free resume checker shows which keywords your resume is missing.

• Restored a 3 TB production Oracle database to a point in time in 42 minutes after a faulty batch job, with no data lost past the agreed recovery point.
• Tuned the 20 slowest claims queries using AWR reports and new composite indexes, cutting average report run time from 11 minutes to 50 seconds.
• Upgraded 35 SQL Server instances from 2016 to 2022 over 4 months, each within a 2-hour weekend window.
• Replicated 12 PostgreSQL clusters with Patroni and streaming replication, bringing automatic failover time under 30 seconds.
• Patched 90 Oracle and SQL Server instances every quarter on schedule, closing all critical database findings in two consecutive audits.
• Audited database access across 70 instances and removed 140 shared and orphaned logins before a PCI DSS assessment.
• Automated nightly restore verification for 50 databases with PowerShell and dbatools, catching 3 corrupt backups before they were needed.
• Partitioned a 1.4 billion-row transactions table by month, cutting nightly maintenance from 5 hours to 70 minutes.
• Migrated 40 on-premises databases to Amazon RDS with logical replication, each cutover finished in under 20 minutes of downtime.
• Set up Always On availability groups for 8 critical SQL Server databases, raising measured availability from 99.5% to 99.95%.

• Lead with the engine the posting runs

  Read the posting for the main engine and version, then make it the first word of your headline and the first skill group. If they run SQL Server and you are mostly Oracle, show the SQL Server work you have and the transferable parts: backups, availability groups, tuning method. Do not claim depth you lack. Tailor your DBA resume

• Use the cover letter for a recovery story

  One short account of a real recovery or upgrade tells a hiring manager how you work under pressure: what failed, how quickly you restored service, what you changed afterward. Add the size of the estate you run and the engine versions. Close by naming the part of their environment you would review first. Generate a DBA cover letter

• Prepare for scenario questions on failure

  Expect questions such as: the primary is down, what do you check first? A query got slow overnight, how do you find out why? How do you upgrade a major version with little downtime? Practice answering in order, with the commands or views you would use and when you would escalate. Practice DBA interview scenarios

• Choose a layout that keeps versions readable

  DBA resumes carry many engine names, versions and tools. A clean single-column template with a clear skills section keeps them easy to scan and parse. Group by engine, put versions in the same line and avoid tables or icons that can garble the text when an applicant system reads the file. Browse resume templates