Database Administrator CV: what to include

Updated 17 September 2026 · 2 min read

A database CV is read for trust. Panels want to know which systems you have been responsible for, what you have recovered, and whether you understand the platforms they run. This guide explains how to show that clearly and honestly.

How this guide was made

Written for this site with AI assistance, then checked automatically before publishing. The topic table, sample questions, worked examples and study plan are generated from this site’s question bank: each worked example is recalculated by separate code, and each sample answer says where it came from.

The guide deliberately states no salaries, grades, pass marks or exam dates. Those change, and they could not be checked here, so take them from the advert itself.

This site is independent and is not affiliated with MIFOTRA or any employer.

Lead with responsibility and scale

Open with a short profile naming your platforms, years of experience and the kind of systems you have administered. For each post, state the scale: number of instances, data volume, the criticality of the systems and whether you were on call for them. "Administered twelve PostgreSQL and SQL Server instances supporting core banking reporting" places you immediately.

Put recoveries and incidents in writing

This is the section that distinguishes candidates. Describe recoveries you performed, the cause, the recovery time and what changed afterwards. Include performance work with before and after figures where you have them, and migrations you completed without data loss.

Name the platforms honestly

List the engines and versions you have worked with and be clear which you administer daily and which you have only used. Interviews probe this section closely, and an overstated platform is quickly exposed.

Show the operational practices

Mention backup strategies you designed, restore testing routines, replication or clustering you configured, access reviews you carried out, and automation you wrote. These show an administrator who prevents incidents rather than only responding to them.

Quantify the estate you have looked after

Panels read database CVs for scale, because running one small application database is a different job from running forty. Give numbers where you can: how many instances, how large the biggest database is, how many users or applications depend on it, and whether it runs around the clock. A line saying you ran a system that could not be down during business hours tells a panel more about your working life than any list of features.

Be precise about shared responsibility

Where you worked in a team, say which part was yours. Panels ask, and an honest answer lands far better than a claim that collapses under one follow-up question.

Structure

Contact details and a three-line profile.
Experience, most recent first, with scale, platforms and outcomes.
Education and certificates with dates.
Technical skills grouped by platform, tooling and practices.
Referees, ideally including someone who saw you handle an incident.

Mistakes to avoid

Listing platforms with no indication of depth.
Describing duties without a single outcome or incident.
Omitting recovery experience, which is the first thing panels look for.
Including real table or system names that should stay confidential.
Unclear dates that hide how long you have actually administered databases.

Open adverts for this position

No open Database Administrator advert matched when the jobs board was last checked. It is refreshed every morning.

Browse every open vacancy

Common questions

Should I mention databases I only queried as a developer?

Yes, clearly labelled as development use. It shows SQL depth without claiming administration you have not done.

How do I show experience if my organisation uses managed cloud databases?

Describe what you own in that environment: schema design, tuning, access control, backup policy, cost and recovery testing. Those remain the administrator's responsibility.