Senior Database Reliability Engineer

About the role

We're looking for a Senior Database Reliability Engineer who thinks like a data engineer, not just a DBA — someone who treats data as a platform, not a collection of instances to keep patched. You'll own the reliability, performance, and architecture of our database estate across multiple technologies (relational, NoSQL, caching, time-series, and warehouse), and you'll be a standing voice in architectural and product decisions about how data is stored, moved, and consumed across the organization — not just called in after the design is finalized. You'll also own the health of our database environments themselves — debugging and improving the tooling, provisioning, and developer experience around data, so engineering teams can move fast without fighting the platform. In this role, you'll be part of a team of engineers and technology experts, delivering mission-critical services that help our customers manage, protect, and maintain millions of endpoints and servers. You will have the opportunity to design and develop high-availability software systems that support our global operations. We are flexible on remote working from home, if you are located in the USA and reside in one of the following states - CA, CO, CT, FL, GA, *IL, KS, ME, MA, MD, NJ, NC, NY, OR, TN, TX, VA, OH and WA. We have physical offices in Austin, TX and Tampa, FL, if you prefer a hybrid option. Onsite interviews may be required for this role.

Responsibilities

• Own architectural and lifecycle decisions for the data domain — technology selection, deprecation, capacity planning, and long-term platform direction — as a standing collaborator with Architecture, not an implementer brought in after decisions are made
• Design, operate, and evolve database platforms across multiple technologies: relational, or equivalent time-series stores and data warehouse systems
• Partner with Architecture and Engineering on product and feature decisions that touch data — schema design, access patterns, scalability tradeoffs — early in the design process
• Debug and resolve environment and developer-experience issues across database tooling, provisioning, and local/CI data infrastructure — reduce friction for engineering teams working with data
• Collaborate with Architecture on expanding the technology footprint of the data platform — evaluating and