Database Administrator resume
What the hiring manager reads first
All roles Software engineering Reading notes, not rules
Summary
An engineering manager usually looks first for what the candidate built or worked on, the system around it and the stack it ran on.
Also posted as: dba, database engineer, sql server dba, oracle dba, postgresql dba, sql developer, database developer.
See a sample applicationNot taking applications yet.
Read first
- Databases run: engines, size, uptime
- Performance tuning results
- Backup, recovery and migrations
- Security and access work
One line, before and after
Original: Ran 14 PostgreSQL databases, the largest 3 TB. Rewrote the slowest reporting queries, which cut their run time from 40 minutes to 4.Suggested: Cut the slowest reporting queries from 40 minutes to 4 by rewriting them, across 14 PostgreSQL databases up to 3 TB.
Why this changedThe tuning result leads; the size of the estate frames it. Every figure in the rewrite is in the original line; nothing is added.
Section order
- Summary
- Experience
- Certifications
- Skills
- Education
Where your resume has these sections. A section your resume does not have is not added.
Mistakes that cost interviews
- Engine lists without the size of what you ran
- A wall of technologies with no context
- Team achievements written as personal ones
- Seniority words the resume does not support
Evidence that counts in software engineering
- Systems or features worked on, and the candidate's part in them
- Scale: users, requests, data volume, latency, cost
- Measured effect on reliability, performance or cost
- Stack named where it was used, not only in a skills list
- Code review, mentoring and design work for senior roles
- Shipped side projects or open source for early careers
Use what your resume already shows. A line without a number can still be strong when it says clearly what you did and where.
These are common reading conventions drawn from hiring guides and career services, not rules every employer follows.