How to write a database administrator resume summary
Name your engines and the size of the estate you run, and add one result.
- Junior database administrator (entry level)
- Junior database administrator with two years supporting PostgreSQL and SQL Server for a logistics company. Looks after 40 production databases and runs nightly backups with a 99% success rate.
- Senior database administrator (mid level)
- Senior database administrator with seven years running PostgreSQL and SQL Server in retail and logistics. Looks after 120 databases and holds 99.99% availability on the order database.
- Head of database engineering (senior)
- Database engineering leader with 15 years in finance and distribution. Leads 14 engineers responsible for 900 databases and cut database cost by 28% in three years.
| Instead of | Write |
|---|---|
| Experienced database professional with a passion for data and a strong track record of reliability. | Senior database administrator for PostgreSQL and SQL Server, holding 99.99% availability on an order database across 120 databases. |
If you give 99.99%, know whether it covers planned maintenance, since a DBA interviewer will ask.
Summary or objective?
Anyone who has supported a production database, including in an internship or support role, should use a summary.
Graduates and career changers can use an objective: "Information systems graduate seeking a junior DBA role; built and restored a PostgreSQL practice environment of 10 databases."
Resume headline examples
Database roles are usually filtered by product, so the engines you run belong next to your title.
- Junior Database Administrator | PostgreSQL, SQL Server, backups (Entry)
- Senior Database Administrator | PostgreSQL, SQL Server, Amazon RDS (Mid)
- Database Administrator | AWS migrations, high availability (Cloud)
- Head of Database Engineering | Data platform reliability and cost (Senior)
Experience bullets that show results
Start with the databases you looked after, then what got faster, safer or cheaper.
| Instead of | Write |
|---|---|
| Managed databases. | Support 40 production PostgreSQL and SQL Server databases serving the warehouse and shipping systems. |
| Improved query speed. | Rewrote 15 slow report queries and added six indexes, cutting the longest report from 14 minutes to 90 seconds. |
| Handled backups. | Rebuilt a restore test that runs monthly, proving a 300 GB database can be recovered in under 50 minutes. |
| Worked on cloud migration. | Moved 35 databases to Amazon RDS and Aurora PostgreSQL with under 15 minutes of downtime each. |
| Reduced database costs. | Cut database cost by 28%, about $3.1 million a year, through consolidation, licence review and storage tiering. |
| Did upgrades. | Upgraded 60 PostgreSQL databases two major versions with under five minutes of downtime each. |
| Managed access. | Replaced shared database logins with named, audited accounts for 300 users, closing an audit finding. |
Missing a number? Write a bracket now, such as "cut the run from [X] to [Y] minutes", and check the figure in your team's dashboards or tickets before you send. A bracket you can't fill means the bullet needs rewriting.
Bullet ideas by area
Bullets for the work most often hired for. Swap in your figures where the brackets are and keep only the work you have done.
Availability and recovery
- Held [database] at [X]% availability for [Y] months using [method]
- Brought recovery time for [X] systems from [Y] hours to [Z] minutes
Performance
- Cut peak CPU on [cluster] from [X]% to [Y]% by fixing [Z] costly queries
- Rewrote [X] slow queries, reducing [report] from [Y] minutes to [Z] seconds
Migration and cost
- Moved [X] databases to [platform] with under [Y] minutes of downtime each
- Reduced database spend by $[X] a year by [method]
Upgrades and access
- Upgraded [X] databases from [version] to [version] with [downtime]
- Moved [X] users to named, audited accounts
Skills and keywords for a database administrator resume
Keep to the engines and tools you could defend in a technical interview, grouped by purpose.
Databases
PostgreSQL, SQL Server, Oracle, MySQL, Amazon RDS, Aurora
Reliability
Backup and recovery, High availability, Disaster recovery testing, Replication
Performance
Query tuning, Indexing, Execution plans, Capacity planning
Tools
Terraform, Python, Bash, Flyway, Query Store
Practices
Change control, Runbooks, On-call, Security and access control
Matching the database administrator job description
Ads name engines, such as SQL Server, Oracle or PostgreSQL. Put the ones you run in your headline.
If the ad stresses cloud, lead with managed database work; if it stresses performance, lead with tuning results.
Use the ad's tool names where you've used them.
Certifications and how to list them
No licence is needed, and few DBA ads require a certificate. A cloud or vendor certificate can help if an ad names that platform and your work hasn't used it much.
| Credential | Earned | In progress |
|---|---|---|
| AWS Certified Solutions Architect - AssociateAmazon Web Services | AWS Certified Solutions Architect - Associate, AWS, [year] | Exam scheduled for [month year] |
- AWS Certified Solutions Architect - Associate: AWS recommends at least a year of hands-on experience designing cloud solutions on its services. Valid for 3 years. AWS, Solutions Architect - Associate
Certificate, master's or MBA: what helps a database administrator
A bachelor's in computer science or information systems is the common route in. Many DBAs start in development, data analysis or system administration and move over once they've run a production database.
If you take a certificate, pick the one for the engine or cloud the ads name, and list it with the year.
A master's in data management, computer science or information systems suits a move toward data architecture. On the management side, some organisations require or prefer a graduate degree for computer and information systems managers, in computer science, information technology or business administration.
A certificate goes in its own section with the year, and one in progress as "DP-300, exam scheduled [month year]".
Database Administrator resume with no experience
Show database work you've done: SQL in a developer or analyst job, a lab with backups and restores, or support work on a database system.
- Build a lab with replication, backups and a tested restore.
- Give data size and recovery time.
- List SQL or reporting work from other jobs.
- Script one routine task and link the code.
- Add a cloud or vendor database certificate if you've earned one.
Moving up: DBA, senior, head of database engineering
Database administrator. Open with your engines, how many databases you support and a tested restore.
Senior DBA. You own the platform. Upgrades and migrations you led, with their downtime, come first, then tuning results.
Head of database engineering. Give the team size and the estate, then the decisions: which engines and cloud services you chose, and what that did to cost.
Database administrator resume format and length
One page suits most administrators. Heads of engineering can use two if the second page adds relevant systems and teams.
Write engine names in plain text so screening software can match them.
Questions
What should a database administrator resume include?
Your engines, the databases you support and their size, and results for availability, recovery, performance and automation. Add security work, such as access reviews and encryption. List certificates with the year. Group the skills section by engine, cloud and tools.
How do I show impact without large numbers?
Use other measures: restore tests passed, recovery time, query speed before and after, manual tasks automated or upgrades finished without downtime. Relative figures work, such as "halved backup time". A small estate run well, with clear results, reads better than vague claims.
Should I list every database I've touched?
No. List the engines you could run in production, with the one the ad names first. Group others as "also supported". A DBA interview often includes a question on the internals of each engine listed, such as how it handles locking or replication, so cut any you couldn't explain.
How do I show backup skill at a junior level?
Describe backups you ran and, more importantly, restores you tested: "tested monthly restores for 40 databases, cutting recovery time from four hours to one". A schedule only proves backups were taken. A tested restore, with the time it took, proves the data comes back.
Which certification is best for a database administrator?
The one for the engine in the ads you want. For SQL Server on Azure, that's Microsoft's Azure Database Administrator Associate (exam DP-300); Oracle shops look for Oracle's own certifications. None is usually required, and it's most useful when you're moving to an engine you haven't run in production. Once you run that platform at work, your uptime and recovery results say more.
Do I need a degree?
Many ads ask for a bachelor's degree in computer science, information systems or a related field. Some employers hire on experience instead, especially for DBAs who came up through development or support. Without a degree, lead with your work and any current certificates, and put education last.
Is a master's or MBA worth it for a DBA?
For DBA jobs themselves, experience counts most. A master's in data management or computer science pays off on the way to data architecture. For IT management, an MBA or a master's in technology management is the usual choice. Either can be studied part-time and listed as "expected [year]".
How do I show I'm ready for senior or head of database engineering?
Show a standard or platform that changed how the team works, such as automated patching or a migration you led. Add DBAs you trained and any on-call or change process you set up. Early roles can drop to a line each.