Exemplo de CV para Database Administrator

Choose the right format for a Database Administrator resume

Use a reverse-chronological format. Hiring managers and applicant tracking systems both expect it, and DBA roles are heavily experience-driven — your most recent position carries the most weight. A functional or hybrid format raises red flags unless you are making a significant career pivot.

Keep the resume to one page if you have fewer than ten years of experience, two pages if you have more. Use clean section headers (Summary, Experience, Skills, Education, Certifications), a standard font like Calibri or Georgia at 10–12 pt, and consistent date formatting. Avoid tables and text boxes — many ATS parsers strip them out entirely.

• File format: submit as .docx or PDF depending on the job posting; .docx parses more reliably in older ATS platforms
• Margins: 0.75–1 inch on all sides to maximize readable space without crowding
• Section order: Summary → Skills → Experience → Certifications → Education

Write a professional summary that positions you as a specialist

Your summary is three to four lines that tell a hiring manager your database platform expertise, years of experience, and one or two concrete contributions. Generic phrases like 'results-driven professional' waste space. Name the platforms you own — Oracle, SQL Server, PostgreSQL, MySQL, MongoDB — and lead with a number if you can.

Example: "Oracle-certified DBA with 9 years managing enterprise databases up to 40 TB across financial services environments. Reduced unplanned downtime by 60% over two years by implementing proactive monitoring with Oracle Enterprise Manager and redesigning backup strategies using RMAN. Experienced in RAC, Data Guard, and performance tuning complex OLTP workloads."

Write work-experience bullets that show impact, not just duties

Every bullet should answer: what did you do, with what tool or method, and what happened as a result? Recruiters reviewing DBA resumes want to see query optimization, high-availability architecture, backup and recovery, and capacity planning — with numbers attached. Avoid writing 'responsible for database maintenance'; instead, say what you maintained, how large it was, and what your work produced.

Start each bullet with a strong action verb: tuned, migrated, automated, architected, reduced, consolidated, implemented. Quantify wherever possible — database size, query performance improvement, uptime percentage, storage savings, or team size.

• Tuned 200+ slow-running queries in SQL Server 2019 using execution plan analysis and index optimization, cutting average report generation time from 4.2 minutes to 38 seconds for a 500-user ERP system.
• Architected and managed a 3-node Oracle RAC cluster on OCI supporting 6 TB of transactional data, maintaining 99.97% uptime over 18 months and eliminating two planned maintenance windows per quarter.

Skills and certifications recruiters and ATS look for

Build a dedicated Skills section that lists platforms, tools, and competencies as discrete keywords — not buried in paragraph text. ATS systems parse this section directly. Separate database platforms from adjacent tools so recruiters can scan quickly. Certifications belong in their own section or immediately after your name in the header if they are highly recognized.

Prioritize certifications that hiring managers actually filter on: Oracle Database certifications (OCA, OCP, OCM), Microsoft Certified: Azure Database Administrator Associate (DP-300), AWS Certified Database Specialty, and MongoDB Certified DBA Associate. The DP-300 is increasingly requested as cloud migration projects dominate job postings.

• Database platforms: Oracle 19c/21c, SQL Server 2016–2022, PostgreSQL, MySQL, MariaDB, MongoDB, Cassandra
• Cloud and managed services: AWS RDS, Aurora, Azure SQL Database, Google Cloud SQL, Oracle Cloud Infrastructure
• Tools: RMAN, Oracle Enterprise Manager, SQL Server Management Studio, pgAdmin, Percona Toolkit, Redgate, Liquibase
• Core competencies: performance tuning, high availability (RAC, Always On, replication), disaster recovery, capacity planning, query optimization, data modeling
• Scripting: T-SQL, PL/SQL, Bash, PowerShell, Python (for automation and monitoring scripts)

Education, licenses, and extras that round out the resume

A bachelor's degree in Computer Science, Information Systems, or a related field is the standard expectation for mid-to-senior DBA roles. If your degree is unrelated, your certifications and experience carry more weight — list them prominently. Include your GPA only if you graduated within the last three years and it is above 3.5.

Add a separate Certifications section with the certification name, issuing body, and year earned. If a certification expires, include the renewal date. For senior roles, a brief line noting security clearance, HIPAA or PCI-DSS compliance experience, or on-call availability can differentiate you — these are real operational requirements that many DBA job descriptions list explicitly.

• List certifications in reverse order of relevance, not date
• Include vendor training completions (e.g., Oracle University courses) only if you lack a formal certification
• Professional memberships like DAMA International or PASS are worth one line but should not take up significant space

Mistakes to avoid

• ×Listing database platforms without version numbers forces recruiters to guess whether your Oracle experience is 11g or 21c, which matters enormously for cloud migration and licensing roles.
• ×Writing bullets that describe job duties rather than outcomes — 'managed backups' tells a hiring manager nothing compared to 'designed and tested a RMAN backup strategy that reduced recovery time objective from 4 hours to 45 minutes for a 12 TB production database'.
• ×Omitting cloud platform experience even when it is limited — if you have deployed a single RDS instance or migrated one workload to Azure SQL, include it, because cloud fluency is now a baseline expectation in most DBA job postings.
• ×Burying certifications at the bottom of a two-page resume when they are among the strongest signals a DBA candidate can send — Oracle OCP or DP-300 should appear in the header or immediately after your summary.

Frequently asked questions

Should a Database Administrator resume include both SQL Server and Oracle experience, or focus on one?

Focus on the platform the target job requires, but do not hide secondary platform experience. If a posting specifies Oracle, lead with Oracle throughout your summary and bullets, then list SQL Server in your skills section. Trying to appear equally strong in both when you are not will surface quickly in a technical interview.

How do I show DBA experience if I have been an embedded member of a development team rather than a dedicated DBA?

Use your job title as listed on your contract or HR record, then clarify scope in the first bullet of that role — for example, 'Served as sole database owner for a 15-developer team, managing schema design, query performance, and production deployments across PostgreSQL 14 and Redis.' Quantify the database size, user load, or transaction volume to establish credibility.

Is a two-page DBA resume acceptable?

Yes, for candidates with more than eight to ten years of experience, two pages is standard and expected. The rule is that every line must earn its place — cut early-career roles to two or three bullets each and remove skills that are no longer relevant to the roles you are targeting. Never pad a one-page resume to two pages just to appear more experienced.