Data & AI
Database Administrator (DBA) Resume Examples & CV Template (Entry to Senior)
Database Administrators keep the databases behind applications fast, secure, available and recoverable. This guide explains what the job involves, which skills employers check for, how to write a CV that passes ATS screening, and how to prepare for the interview.
What the role does
A Database Administrator (DBA) installs, configures, secures and maintains the databases that applications and business teams depend on. In practice that means tuning slow queries and indexes, planning backups and testing restores, setting up replication and failover for high availability, managing users and permissions, monitoring health and capacity, and carrying out upgrades and migrations with little or no downtime. DBAs work with relational databases such as PostgreSQL, MySQL, SQL Server and Oracle, often alongside NoSQL stores such as MongoDB or Redis, and increasingly with managed cloud databases such as Amazon RDS and Aurora, Google Cloud SQL or Azure SQL. They use scripting (Bash, Python) and tools such as Ansible and Terraform to automate routine work. They work closely with backend developers who write queries and schemas, DevOps and infrastructure engineers who run the platform, data engineers who read from the databases, and security and compliance teams. The role exists in almost every company that stores important data, from banks, telecoms and e-commerce to healthcare, logistics and SaaS.
Main responsibilities
- Install, configure and upgrade database servers and plan capacity for data growth
- Tune slow queries, indexes and configuration so applications meet their latency targets
- Design and test backup and restore procedures that meet agreed recovery time and recovery point objectives
- Set up replication, failover and disaster recovery for high availability
- Manage users, roles and permissions, encryption and audit logs to protect sensitive data
- Monitor database health, storage, connections and locks, and respond to incidents and on-call alerts
- Plan and run schema changes, version upgrades and migrations (including to the cloud) with minimal downtime
- Automate routine tasks with scripts and infrastructure as code, and work with developers on schema design and data ownership
Career path
- 10-2 yrsIntern / Junior Database Administrator
Handles routine tasks such as backups, user management and monitoring with guidance and learns the systems and runbooks.
- 22-4 yrsDatabase Administrator
Owns production databases, tuning, backups and upgrades, and handles on-call for database incidents.
- 34-7 yrsSenior Database Administrator
Designs high-availability and disaster recovery architecture, leads migrations and tuning across teams and mentors others.
- 47+ yrsLead DBA / Database Architect
Sets database standards, platform choices and data reliability strategy across the company.
- 58+ yrsInfrastructure Manager, Data Platform Lead or Site Reliability Engineer
Either leads people and the data platform, or moves into reliability and architecture roles at the highest level.
Skills employers ask for
Hard skills
- SQL and database fundamentals
- Advanced SQL, indexing, transactions, isolation levels, locking and normalization.
- Relational database administration
- PostgreSQL, MySQL, SQL Server or Oracle: installation, configuration, storage and day-to-day operations.
- Performance tuning
- Execution plans, index design, query rewriting, configuration tuning and finding the real bottleneck.
- Backup and recovery
- Full, incremental and point-in-time recovery, restore testing and meeting RTO and RPO targets.
- High availability and replication
- Streaming replication, clustering, failover tools such as Patroni, Always On or Data Guard, and disaster recovery.
- Database security
- Roles and least privilege, encryption at rest and in transit, auditing and compliance requirements.
- Monitoring and troubleshooting
- Prometheus, Grafana or vendor tools to watch locks, connections, replication lag, storage and slow queries.
- Automation and scripting
- Bash and Python, Ansible and Terraform to automate provisioning, patching and routine maintenance.
- Cloud databases
- Amazon RDS and Aurora, Google Cloud SQL or Azure SQL: sizing, cost, parameter groups and managed backups.
- Migrations and upgrades
- Schema change strategy, version upgrades, data migration tools and zero or low downtime cutovers.
Soft skills
Tools
Certifications
Open jobs right now
Latest Database Administrator jobs
CV examples
CV summary examples
Junior Database Administrator with a 6-month internship managing PostgreSQL and MySQL backups, monitoring and tuning. Cut report query time from 14 s to 2 s, automated backups for 15 databases and built Grafana dashboards that caught 4 storage issues early.
Database Administrator with 4 years running PostgreSQL, MySQL and SQL Server for payments and e-commerce. Keeps 40 production instances at 99.99% availability, cut p95 query time from 800 ms to 120 ms and cut database cost by 28%.
Senior Database Administrator with 9 years in banking and telecom. Owns the data platform behind 200 databases and 40 TB, designed disaster recovery with recovery time under 15 minutes, cut database cost by 40% and grows DBAs through mentoring.
Experience bullet examples
Administered 40 PostgreSQL and MySQL production instances (8 TB) with 99.99% availability over 12 months
Tuned the top 30 queries of the payments database, cutting p95 query time from 800 ms to 120 ms during peak traffic
Built a Patroni high availability setup with automatic failover in under 30 s, replacing a manual 40-minute process
Cut storage and instance cost by 28% ($3k a month) with right-sizing, partitioning and archiving old data
Automated nightly backups for 15 databases and ran monthly restore tests with a 100% success rate
Introduced weekly restore tests and point-in-time recovery drills, cutting recovery time from 6 hours to 90 minutes
Upgraded 6 production databases from PostgreSQL 12 to 15 with logical replication and under 2 minutes of write downtime each
Tuned a month-end billing batch from 9 hours to 3 hours with partitioning and parallel execution
Cut the time to create a new production database from 5 days to 2 hours with Terraform and Ansible
Mentored 4 DBAs; 2 were promoted within 18 months
How to write your CV
Put numbers in every bullet you can
Query time, availability percentage, database size, recovery time, backup success rate, cost savings, downtime. Numbers show the scale of the systems you protect and what changed because of you.
Write action, method and result
Start with a strong verb, say how you did it, end with the result: "Cut p95 query time from 800 ms to 120 ms with index redesign and query rewrites."
Show reliability, not only daily tasks
Tested restores, failover drills, uptime and recovery times are what separate a strong DBA CV from a list of duties. Show what stayed up and recovered because of your work.
Show your stack inside the bullets
"Built a 3-node PostgreSQL cluster with Patroni and HAProxy" says more than a list of products. Keep a short skills section as well, so ATS software finds the exact keywords.
Show cost, security and automation
Savings from migrations and right-sizing, passed audits and hours saved with scripts show engineering maturity, which is what separates a mid-level CV from a junior one.
Match each job description
Use the same terms as the posting ("PostgreSQL", "Oracle", "high availability", "backup and recovery") where they are true for you, and move the most relevant experience to the top. Keep it to one page under 5 years of experience.
Interview questions
TechnicalA production query suddenly became slow. How do you find and fix the problem?
How to answer: Check what changed first. Look at the execution plan, statistics, missing or unused indexes, locks and resource usage. Fix with an index or rewrite, measure before and after, and add monitoring so you catch it earlier next time.
TechnicalHow would you design a backup and recovery strategy for a critical database?
How to answer: Ask for RTO and RPO. Combine full, incremental and log or WAL backups for point-in-time recovery, store copies off-site, encrypt them, and test restores regularly because an untested backup is not a backup.
TechnicalHow does replication work and how would you set up high availability for PostgreSQL or MySQL?
How to answer: Explain primary and replicas, synchronous versus asynchronous trade-offs, replication lag, automatic failover tools (Patroni, orchestrator), a connection proxy and how to avoid split brain.
TechnicalWhat are transaction isolation levels and what problems do they prevent?
How to answer: Cover read committed, repeatable read and serializable and the anomalies they prevent (dirty, non-repeatable and phantom reads). Mention the performance and locking trade-offs and the default level in the database you know.
TechnicalHow do you design indexes, and when can an index hurt performance?
How to answer: Index columns used in filters, joins and sorting, and consider composite and covering indexes. Too many indexes slow writes and use storage, and low-selectivity or unused indexes add cost without benefit. Verify with execution plans.
TechnicalHow would you upgrade a large production database with minimal downtime?
How to answer: Test in a copy first, take and verify a backup, use logical replication or a replica-based switchover, plan the cutover and rollback, schedule a low-traffic window and verify with application checks afterwards.
TechnicalHow do you secure a database that holds sensitive customer data?
How to answer: Least privilege roles, no shared accounts, encryption at rest and in transit, network restrictions, audit logging, regular patching, masking in non-production environments and periodic access reviews.
BehavioralTell me about a database incident you handled and what you learned.
How to answer: Use situation, action, result: the impact, how you found the cause, how you restored service and what runbook, monitoring or test you added afterwards.
BehavioralDescribe a disagreement with a developer about a schema or query design. What happened?
How to answer: Show that you used data such as execution plans and test results, listened, found a compromise and focused on the shared goal of a fast and reliable application.
BehavioralTell me about a project you are proud of.
How to answer: Pick one with a measurable result. Explain your part, the hardest problem and what you would do differently now.
SituationalThe primary database server crashes during peak hours. What do you do?
How to answer: Confirm the failure and its scope, fail over to a replica or start recovery per the runbook, communicate status to stakeholders, verify data consistency, then write a post-incident review with fixes.
SituationalA developer asks for direct write access to production to fix some data quickly. What do you recommend?
How to answer: Explain the risk, offer a safer path such as a reviewed script run by you, with a backup or transaction and an audit trail, and agree on a process for urgent cases so access stays controlled.
Frequently asked questions
What does a Database Administrator do?
A Database Administrator installs, secures, tunes and maintains databases so that applications and teams can rely on them. They handle backups and recovery, high availability, performance, access control and upgrades.
Is a Database Administrator the same as a Data Engineer?
No. A DBA focuses on the health, performance, security and availability of the databases themselves. A Data Engineer focuses on building pipelines that move and transform data for analytics. In small teams one person often does both.
Is the DBA role disappearing because of cloud databases?
The role is changing rather than disappearing. Managed services handle patching and basic backups, but companies still need people for performance tuning, schema design, security, cost control, migrations and reliability. Many DBAs now work as cloud database engineers or reliability engineers.
Which database should I learn first?
PostgreSQL or MySQL, together with strong SQL and Linux basics. Then add one commercial database that is common in your market, such as SQL Server or Oracle, and one cloud platform.
What should a junior Database Administrator CV include?
Internships, 2 to 3 real projects with links to code or documentation (a replicated PostgreSQL cluster with tested failover and backups), the tools used and measurable results such as query time or recovery time. Add your degree, relevant courses and certifications, and keep it to one page.
How long should a Database Administrator CV be?
One page for up to about 5 years of experience, two pages at most for senior roles. Put the most relevant, measurable work at the top.
Do I need certifications to become a Database Administrator?
Not required, but they help, especially for Oracle and SQL Server roles and for cloud database work. Hands-on projects with backups, replication and tuning matter most, and certifications support them.
Related roles
Build your Database Administrator CV in minutes
Start from an ATS-ready template, let AI improve your bullets, then score your CV and practise the interview out loud.