Someone runs an UPDATE without a WHERE clause at four in the afternoon. A database administrator is the person who knows, without guessing, how far back the data can be restored, how long that will take and which replica to check first. DBAs keep production databases fast, secure and recoverable, and most of their best work is invisible because the disaster it prevented never happens.
This page provides a database administrator job description to copy, followed by how it varies with seniority, the checks that reveal real experience, typical ad errors and advice on contract or permanent hiring. It also draws the line between a DBA, a data engineer and a backend developer, which many job ads blur.
Database administrator job description template
Always name the engine and version family in the brackets. An Oracle DBA and a PostgreSQL DBA overlap in principle but not in daily tooling, so a generic post attracts both and suits neither.
About the role
[Company] is hiring a Database Administrator to look after our [Oracle / SQL Server / PostgreSQL / MySQL] databases running on [on-premises servers / Amazon RDS / Azure SQL Database]. You will own availability, backups, performance and access across [number] production instances, and support developers who build on them. Your manager will be [manager title], and the role is based at [location].
Responsibilities
- Install, configure, upgrade and patch [database engine] across production and non-production environments.
- Design and run backups, including point-in-time recovery, and rehearse restores on a regular schedule.
- Set up and monitor replication and high availability using [Data Guard / Always On availability groups / Patroni / group replication].
- Analyse slow queries through execution plans, then tune indexes, statistics and configuration.
- Investigate blocking, deadlocks and connection exhaustion during incidents.
- Manage users, roles and least-privilege access, including audit logging and encryption settings.
- Plan capacity for storage, memory and connections, and archive or partition data as tables grow.
- Review schema changes and migration scripts from development teams before they reach production.
- Automate routine maintenance and health checks with [Bash / PowerShell / Python].
- Document recovery runbooks and test them with the wider operations team.
Requirements
- [X] years administering [database engine] in production.
- Proven backup and restore experience, including a real recovery under pressure.
- Strong SQL and comfort reading execution plans.
- Hands-on replication and failover experience.
- Good understanding of indexing, locking and transaction isolation.
- Working [Linux / Windows Server] administration.
- Scripting ability for maintenance and monitoring.
Nice to have
- Experience with managed services such as Amazon RDS, Aurora or Azure SQL Database.
- Exposure to a second relational engine.
- Experience of migrating between engines, for example from Oracle to PostgreSQL.
- Infrastructure as code for provisioning database instances.
What we offer
- [Remuneration] and [benefits package].
- [Work pattern], including [maintenance windows and on-call cover].
- [Vendor training or certification funding].
How the database administrator role changes by level
Junior DBA
A junior monitors jobs, checks that backups succeeded, handles access requests and runs prepared scripts for routine maintenance. Many come from development support or a systems role. Ask for sound SQL and a real curiosity about how databases work, and supervise anything touching production.
Mid-level DBA
A mid-level DBA owns a set of instances: patching, tuning, restores and failover tests. Requirements should cover reading execution plans without help, handling blocking in production and taking part in on-call.
Senior DBA
Seniors design replication topologies, plan major version upgrades and engine migrations, and set standards for schema changes and access. They also work closely with architects and developers on data models for high-traffic tables, and decide when a problem needs a query change and when it needs hardware.
Lead DBA or database reliability engineer
This person treats a large fleet as code, with automated provisioning, failover and observability. It suits companies running many instances. If your estate is small, the title will promise work that does not yet exist, so reserve it for real scale.
Database administrator skills that matter most, and how to check them
- Recovery. Ask them to restore a database to the minute before a bad update, on your engine. On PostgreSQL that means a base backup plus WAL replay, on Oracle RMAN with archived redo logs, and on SQL Server a full backup followed by log backups.
- Query tuning. Share a real execution plan with a poor join order or a missing index, and ask what they see. Good DBAs talk about cardinality estimates, statistics and selectivity before they suggest adding an index.
- Concurrency. Ask how they would find out why an application froze for a few minutes this morning. Look for familiarity with lock views, blocking chains and long-running transactions, along with engine-specific sources such as Query Store on SQL Server or lock-wait logging on PostgreSQL.
- Engine-specific maintenance. For PostgreSQL, ask about autovacuum and bloat. For MySQL, ask how replication lag is diagnosed. For Oracle, ask how they use an AWR report. Vague answers suggest the experience sits on another engine.
- Security. Ask how they would give an analyst read access to production data that contains personal details. Sensible answers mention least privilege, masking or a read replica, and auditing.
The strongest single question is about a restore that did not go as planned. Anyone who has done this seriously will remember the details, including what was missing from the runbook.
Common database administrator job description mistakes
- Writing database admin when you mean data engineer. Pipelines, warehouses and transformations are a different skill set from uptime and recovery. Fix: if the job is moving data into analytics, post a data engineer role.
- Listing all engines equally. Oracle, SQL Server, PostgreSQL and MySQL as equal essentials suggests you do not know what you need. Fix: name a primary engine and mark others as helpful.
- Assuming a managed service removes the role. Providers handle much of the patching and backup plumbing, but query design, access, cost and recovery planning remain yours. Fix: say which tasks your provider covers and which stay in-house.
- Not mentioning maintenance windows. Upgrades and failover tests often happen at night or on weekends. Fix: state how often and how the time is recognised.
- Ignoring the state of the estate. Running a stable, well-tuned cluster differs from rescuing ageing instances with no restore history. Fix: describe the current position and the first problem you want solved.
Contract, contract-to-hire or permanent: which suits a database administrator
Contract DBAs work well for engine migrations, major version upgrades, performance rescues and setting up high availability for the first time. These jobs reward someone who has done the same upgrade path before. Keep tight control of production credentials, and ask for updated runbooks before the engagement ends.
Contract-to-hire suits a company hiring its first DBA, which often lacks anyone to assess the role. A trial on your real databases shows whether the person improves things carefully or changes settings without measuring the effect.
Permanent hiring fits businesses where the database is central and the person must learn its data, its heavy queries and its seasonal patterns over time. Zilo AI can help whichever suits you, and we hire database administrators in India on contract, contract-to-hire or permanent terms, across Oracle, SQL Server, PostgreSQL and MySQL. The IT talent overview shows other infrastructure and data roles.
Frequently asked questions
What should a database administrator job description include?
Specify the engine, hosting model, number and size of instances, the high availability setup and the recovery targets. Then outline on-call expectations and the current priority, such as an upgrade or a tuning backlog.
What is the difference between a DBA and a data engineer?
A DBA keeps database systems available, secure, fast and recoverable. A data engineer builds pipelines that move and shape data for analytics and machine learning. The DBA looks after the engine and the data engineer looks after the flow of data, and the two sometimes work together on replication or extraction load.
How is a DBA different from a backend developer?
A backend developer writes the application and its queries. The DBA looks after how those queries behave in production, reviews schema changes and handles backups and failover. Small teams often let developers do both until the first serious incident.
Do we need a DBA if we use a managed database service?
Often you do, though perhaps not full time. Managed services cover much of the infrastructure work, but somebody still has to tune queries, design access, plan recovery and control cost. A contract DBA can be enough for smaller estates.
Should a DBA be certified?
A vendor certification can help, particularly for Oracle roles, where some employers look for one. Treat it as a bonus, though, and base your decision on evidence of restores, upgrades and tuning.
If you would like screened DBAs on your preferred engine without running the search yourself, Zilo AI can help. Contact us and tell us about your databases, your hosting and your recovery goals.