Interview Questions to Ask a Database Administrator Candidate
Questions that surface real evidence of data integrity and query performance that the whole application depends on — plus what to actually listen for in the answer, not just whether they say the right buzzwords.
1. A report that used to take seconds now takes minutes. How do you find and fix the cause?
What to listen for: Look for examining the query plan, indexes, statistics, locking, and data growth, then testing a change safely before applying it to production.
2. How do you prove that your backups can actually be restored within the time the business needs?
What to listen for: Expect scheduled restore tests, documented recovery steps, defined recovery time and data loss targets, and offsite copies, not just successful backup messages.
3. A developer wants direct write access to the production database to fix some bad records. What do you do?
What to listen for: The candidate protects data integrity through least privilege, reviewed scripts, backups before changes, and an audit trail, while still solving the request.
4. Your database is nearly out of storage on a Friday afternoon. How do you decide what to do first?
What to listen for: Good answers cover immediate safe relief, finding the growth source, avoiding risky deletions, escalating if needed, and planning capacity so it does not recur.
5. What would you do in your first 30 days in this database administrator role?
What to listen for: Whether their plan is grounded in the role's actual must-haves (sql/database administration (postgresql/mysql/sql server) and backup and recovery procedures) or generic ("get to know the team"). Specificity here signals real understanding of the job, not just interview prep.
6. Why are you leaving your current role, and why this one specifically?
What to listen for: Forward-looking motivation tied to something concrete about this role, versus badmouthing a past employer or vague dissatisfaction. Watch for whether their reasons actually match what this role offers.
A warning sign in this interview
Has never tested a restore, makes schema changes directly on production without a backup, or treats performance problems as always being the application team's fault.
What to look for on the CV before the interview
Databases managed, size and performance or recovery work.
Confirm before you make an offer
Vendor certifications can help. Ask for performance work done.
People who may apply under another title
This job is also called DBA, Database Engineer, Data Platform Administrator, SQL Administrator. A candidate with one of those titles can be a strong match, so ask the same questions and judge the answers, not the title.
Frequently asked questions
How many of these questions should I ask in one interview?
3-4 is realistic for a 30-45 minute interview once you leave room for follow-ups and the candidate's own questions. Divide competencies across panel members rather than every interviewer asking all of them — see the Interview Scorecard tool for a structured version of this.
How is this different from the Interview Scorecard tool?
This page is a generic starting point for the database administrator role. The tool generates a full panel-ready kit — competency-grouped questions, a 1-5 rating rubric, and strong/weak answer examples — tailored to your actual job description and competencies.
What is a red flag when interviewing a database administrator?
Has never tested a restore, makes schema changes directly on production without a backup, or treats performance problems as always being the application team's fault.
What should I confirm before offering a database administrator the job?
Vendor certifications can help. Ask for performance work done.
Hiring a database administrator? The rest of the toolkit
- How to write the job description →
Titles, must-haves, credentials and a starting posting.
- Search strings to find candidates →
Five searches from broad to narrow, with exclusions.
- Run the whole hire in one place →
Jobs, CV review, interviews, offers and checks together.