Database Administrator
Summary
Database Administrator who owns the design, security, and performance of production databases across 26 products for home health, hospice, and senior living software. Day to day: monitoring and tuning databases, managing backups and disaster recovery, patching, capacity planning, and setting database standards with MySQL, Postgres, or SQL Server.
About LivTech
LivTech is transforming how care is delivered to aging adults. We're a high-growth company in the middle of an exciting transformation process - expanding our products, sharpening our focus, and scaling the teams that make it happen. We build the software and solutions that power home health, hospice, and senior living organizations, helping them deliver better, more connected care to the patients, residents, and families who depend on them - work that matters, for the people who need it most.
We hire people who bring our values to life every day: Assuming Positive Intent, Operating with Intensity & Urgency, Being Transparent, and Using Your Power to Make a Difference. If you want to do meaningful work, move fast, and grow alongside a company that's actively reshaping its industry, you'll feel right at home here.
The Opportunity
LivTech is creating a dedicated Database Administrator role to own the design, security, and performance of the databases behind all 26 products across our three business divisions. Today, no single function owns database health enterprise-wide — you'll close that gap, working across divisional engineering teams to raise the bar on reliability, security, and performance.
What You'll Do
Design, implement, and continuously monitor and optimize databases supporting all products across our three divisions.
Plan and maintain backup, disaster-recovery, and logical storage structures for every production database.
Proactively monitor database health, security, and performance, tuning systems to prevent issues before they affect users.
Establish consistent database standards, configuration practices, and documentation across divisions.
Manage patching, capacity planning, and access controls to reduce the risk of data loss or security incidents.
Partner with divisional engineering teams to reduce time spent troubleshooting database problems, freeing capacity for product development.
What You'll Bring
Bachelor's degree in Computer Science, Information Systems, or a related field, or equivalent professional experience.
Four or more years of experience administering production databases, including on-call support responsibilities.
Hands-on experience with one or more major relational database platforms: MySQL, Postgres, or Microsoft SQL Server.
Experience administering multiple relational database platforms and relevant certifications, such as Microsoft Certified: Azure Database Administrator Associate, are a plus.
What We Offer
Alongside competitive pay, we take care of our people with a well-rounded benefits package - think health and wellness coverage, retirement support, paid time off, and more - because feeling supported matters just as much as doing great work.
Learn more about our fast-growing company at .
Skills
As published by ashby · 8 questions · 4 written answers
Basics
Name, Email, Resume
Short answers (2)
- Phone Number
- Have you reviewed the compensation outlined in the job description, and does it fit what you’re looking for?
Pick from a list (2)
- Select all that apply to your relevant experience.
- Which of the following have you personally owned (been the accountable person, not just assisted)? Select all that apply.
Written answers (4)
- Do you have 4 or more years of experience administering production databases, including on-call support responsibilities?
- Are you able to work US-based remote and participate in an on-call rotation that may require responding outside standard business hours?
- Do you have hands-on administration experience with at least one of the following: MySQL, PostgreSQL, or Microsoft SQL Server? If so, please specify which platform(s) and years of experience with each.
- What is your general approach to explaining technical database issues to developers or non-technical teams? (3-5 sentences)