Engineering

Database Administrator Job Description

A Database Administrator, usually shortened to DBA, keeps live databases healthy: available during business hours and out of them, fast enough that applications do not time out, locked down to the people who should have access, and recoverable when something goes badly wrong. It is an operations discipline, distinct from designing the wider estate and distinct from building pipelines. The defining question for the role is not how elegant the schema is but how long it would take to bring the system back after a failure, and whether anyone has actually proved that number recently. Employers evaluating a DBA should push hardest on recovery and on evidence of rehearsal, because a backup that has never been restored is a guess rather than a safeguard, and this is the one area where the cost of a weak hire is measured in lost records rather than lost velocity.

Key skills

Backup strategy plus tested, timed restore proceduresHigh availability: replication, failover, and clusteringExecution plan analysis and index tuningCapacity forecasting for storage, memory, and connection limitsPatching, engine upgrades, and low-disruption maintenance windowsAccess control: roles, privileges, auditing, and encryption at rest and in transitDepth in at least one engine such as PostgreSQL, MySQL, SQL Server, or OracleMonitoring and alerting on locks, replication lag, and slow statements

Responsibilities

  • Keep production databases available, performant, and recoverable within agreed targets
  • Run backups and rehearse restores on a schedule so recovery time is a measured number
  • Configure and prove failover before an incident rather than during one
  • Diagnose slow statements using execution plans and agree fixes with application developers
  • Plan and carry out engine upgrades and security patching with minimal disruption
  • Administer users, roles, and privileges under a least-privilege policy and audit them
  • Forecast storage and connection growth and escalate before it becomes an outage
  • Write runbooks precise enough for a colleague to follow at three in the morning

Requirements

  • Proven experience administering production databases with real availability expectations
  • Deep familiarity with at least one major database engine and its recovery model
  • Demonstrated backup and restore practice, including rehearsed restores
  • Ability to read an execution plan and explain the fix in terms a developer can act on
  • Comfort with scripting for routine administration and monitoring
  • Sound judgement on change windows and risk to live services

Nice to have

  • Experience with managed cloud database services alongside self-managed instances
  • Exposure to a real recovery event and the postmortem that followed
  • Familiarity with a second engine, particularly across the relational and document divide
  • Experience supporting an application through a large migration or version cutover
  • Awareness of audit and retention obligations in a regulated environment

What to look for in a great Database Administrator

Look for someone who is boring in the best sense: methodical, cautious about change windows, and slightly pessimistic about failure. The strongest signal is rehearsal. A candidate who can tell you when they last restored a production backup, how long it took, and what went wrong during the exercise is operating at a different level from one who simply confirms backups run nightly. Pay attention to how they describe working with developers, because a DBA who blocks everything is as expensive as one who blocks nothing. The good ones offer an alternative rather than a refusal.

Interview questions to ask a Database Administrator

The single most useful question is: when did you last restore from a backup, what triggered it, and how long did the restore take? Then ask how they would find out why an application suddenly became slow this morning, listening for a diagnostic order rather than a guess. Ask what they would check in the first hour on a database estate they had never seen. Finally, ask about a change they made that caused a problem and how it was caught. Every experienced administrator has one, and a candidate claiming otherwise is either very junior or not being straight with you.

Where to source Database Administrators

Application developers who became the unofficial owner of the database are a common and often excellent source, since they already understand the workload. Infrastructure and systems administrators with strong storage backgrounds can move across with support on query tuning. Vendor-specific user groups and regional engine communities are active and full of practitioners. Managed service providers and consultancies employ administrators who have seen many estates, which is valuable breadth. Be aware that this is a role where the person may currently hold an unglamorous title, so screen on described duties rather than filtering by keyword alone.

Red flags when hiring a Database Administrator

The clearest red flag is confidence about backups with no experience of restoring them. Be cautious of a candidate who cannot describe a change that went wrong, or who blames developers for every performance problem without describing a conversation that improved things. Someone who insists on manual production access for routine work, and resists any form of automation or peer review, is a risk to both reliability and audit. Watch also for people who have only ever worked on a single engine at a single company and treat its quirks as universal truths, since that inflexibility surfaces quickly.

How an ATS speeds up hiring a Database Administrator

Administrators are often passive candidates who apply to few roles, so a slow or scattered process loses them quietly. Pitch N Hire's ATS keeps every applicant in one pipeline and lets you build a structured interview kit around the things that actually matter here: recovery evidence, incident history, tuning approach, and access discipline. Because a hiring manager, a lead developer, and sometimes a security stakeholder all weigh in, shared scorecards stop the decision hinging on whoever spoke last in the debrief. Reminders and scheduling remove the delays that push a cautious, employed candidate back toward staying put.

Hiring a Database Administrator? See Pitch N Hire on your roles.

FAQ

Hiring a Database Administrator — FAQs

What does a Database Administrator do? +
A Database Administrator keeps live databases running well: monitoring health, taking and testing backups, configuring replication and failover, tuning slow queries, applying patches and upgrades, managing user privileges, and planning for growth in storage and load. The role is accountable for availability and recoverability of the data your applications depend on, and for the procedures that make recovery predictable rather than improvised.
What is the difference between a Database Administrator and a Data Engineer? +
A DBA looks after the operational health of databases that applications write to and read from in real time, focusing on uptime, performance, security, and recovery. A Data Engineer moves and reshapes data into analytical stores so it can be reported on. The skills overlap in SQL and modelling but the accountabilities differ: one is judged on whether the system stays up and can be restored, the other on whether the analytical data arrives correct and on time.
Do we still need a DBA if we use a managed cloud database? +
Managed services take away patching, hardware, and much of the backup mechanics, which genuinely reduces the workload. They do not remove schema and index decisions, query performance, access control, capacity and cost management, or the need to verify that restores work and meet your recovery expectations. Many smaller companies handle this with a developer who has partial ownership. The case for a dedicated administrator strengthens as data volume, uptime expectations, or regulatory obligations grow.
What is the most useful question to ask a DBA candidate? +
Ask when they last restored a production backup and how long it took. It is a single question that separates people who administer databases from people who watch backup jobs succeed. A strong candidate will describe the scenario, the measured duration, what surprised them, and what they changed afterwards. A weak one will reassure you that backups are configured. You do not need database expertise to tell those two answers apart, which makes it an unusually good question for a non-technical interviewer.
What should a Database Administrator job description include? +
Name the engines and versions you run, whether they are self-managed or on a managed service, and roughly how large the estate is. State your availability expectations and whether the role carries out-of-hours or on-call duty, since that materially changes who applies. Mention whether the person will be the sole owner or part of a wider team, and say who they work with on application performance. Practical detail attracts practical candidates and prevents mismatched expectations at offer stage.
Pitch N Hire ATS

Post this job description and track every applicant in one place

Pitch N Hire is an applicant tracking system. Publish this role to your careers page and job boards, then follow every applicant through screening, interviews, and offer without a spreadsheet.

  • Publish to your careers page and job boards from one job record
  • Screen and shortlist applicants against the criteria in this description
  • Move candidates through stages with the whole panel seeing the same view

Free for 1 user · No credit card · Talk to a real hiring expert

Built for recruiters & hiring teams

Ready to hire a Database Administrator?

Post this role to multiple job boards and screen, interview and decide — all in one AI-native platform.

Prefer to talk? Book a demo · Talk to sales · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo