Database Administrator résumé example, in the Console design
A database administrator sample that leads with uptime, recovery time and batch windows rather than a list of versions.
Written for United States, at mid level, in the data & analytics field, shown in the Console design. Every name, employer, address and number below is invented.
Database administrator with eight years keeping transactional systems fast and recoverable, now across 60 instances at an insurer. Cut a nightly claims batch from nearly six hours to under one, and rebuilt disaster recovery around a 15-minute recovery point that is tested every quarter.
Experience
Database Administrator, Stonecreek Mutual Insurance · September 2022 – present
Runs 60 SQL Server and PostgreSQL instances behind claims, policy and billing.
Holds 99.98% availability across two years and 60 production instances, with no unplanned data loss and no failed quarterly restore test.
Cut the nightly claims batch from 5 hours 40 minutes to 51 minutes by rewriting four cursor-driven procedures as set-based operations and re-indexing the claim-line table.
Rebuilt disaster recovery around log shipping with a tested 15-minute recovery point; the failover drill now takes 22 minutes and is run by the on-call rota.
Replaced shared service accounts with per-application credentials and row-level security, closing all 14 database findings from the 2023 audit.
Database Administrator, Crestwater Software · January 2020 – August 2022
Led an eight-month migration of a 4 TB Oracle estate to PostgreSQL, cutting licensing by
60,000 a year with 40 minutes of customer downtime.
Introduced automated restore testing; its first run found three of eleven nightly backups had been failing silently for five weeks.
Tuned the 20 slowest product queries, taking the reporting page from a 14-second median to 900 milliseconds.
Systems Administrator, Calloway Technical Services · June 2018 – December 2019
Supported 400 users and 90 servers, cutting the ticket backlog from 230 to under 30 by scripting the 12 most common requests.
Moved patching from a manual weekend routine to a scheduled pipeline, taking average time to patch from 38 days to six.
Education
B.S. Computer Information Systems · Georgia State University · August 2014 – May 2018
