Staff Database Reliability Engineer

Come work at a place where innovation and teamwork come together to support the most exciting missions in the world! Staff Database Reliability Engineer (DBRE) - Data Platform OpenSearch Must-Have | Distributed Systems | Kafka | Redis | Capacity Engineering | Automation Level Staff DBRE (Senior Individual Contributor / Technical Lead) Domain Distributed Data Platforms Primary Focus Cross-team architecture and systemic reliability for OpenSearch-centered data platforms, with Kafka, Redis, capacity engineering, and Python automation Work Expectations U.S. Eastern Time business hours; on-call participation as required   1.

Summary We are seeking an experienced Staff DBRE with deep OpenSearch/Elasticsearch expertise and strong distributed-systems judgment. The role leads high-impact architecture, reliability, performance, scalability, capacity, and lifecycle improvements across major data-platform services, complemented by Kafka, Redis, Linux, observability, and Python automation. The Staff DBRE solves ambiguous cross-team problems, establishes reusable platform patterns, mentors senior engineers, and influences multiple engineering groups. The scope extends beyond a single cluster or incident while remaining hands-on and evidence-driven. 2. Level Scope and Leadership Expectations Staff DBRE is a senior individual-contributor technical leadership role focused on solving ambiguous, high-impact reliability and architecture problems across platforms and teams. The role has broad influence within the data-platform domain, while enterprise-wide cross-domain strategy remains a Principal-level responsibility. Dimension Expectation at This Level Scope of Ownership Owns complex cross-team reliability, scalability, performance, capacity, architecture, and operational-maturity problems across major OpenSearch-centered platform services. Technical Depth Serves as a domain authority in OpenSearch and distributed-systems failure modes, with strong supporting depth in Kafka, Redis, JVM, Linux, storage, and networking. Engineering Leadership Defines platform-domain patterns, mentors Senior and Lead engineers, raises design-review and incident-analysis rigor, and influences adjacent teams. Automation Architecture Designs reusable Python automation, observability, validation, and lifecycle-management patterns rather than isolated scripts. Execution Drives ambiguous initiatives from problem framing through design, alignment, implementation guidance, and measurable outcomes. Organizational Influence Influences multiple engineering groups through data, production evidence, design standards, and technical judgment; does not unilaterally set enterprise strategy.   3.

A. OpenSearch Platform Architecture • Design and improve large-scale OpenSearch/Elasticsearch topology, dedicated node roles, shard and index strategies, lifecycle management, workload distribution, and recovery patterns. • Solve complex indexing, search, cluster-state, JVM/GC, storage, segment, mapping, allocation, and cross-cluster reliability problems. • Establish domain-level resilience, snapshot, replication, upgrade, and capacity patterns appropriate to the actual scale of the environment. B. Kafka and Redis Reliability • Guide Kafka topology, partitioning, replication, capacity, consumer reliability, and failure-mode remediation for critical services. • Guide Redis Cluster and Sentinel architecture, memory and eviction behavior, persistence tradeoffs, failover, re-sharding, and client reliability. C. Automation, Observability, and Capacity Engineering • Architect reusable Python tooling and safe remediation frameworks for provisioning, validation, maintenance, scaling, and incident prevention. • Define domain-level observability, SLIs/SLOs, capacity models, lifecycle forecasts, and actionable risk thresholds. • Establish Infrastructure-as-Code and operator patterns where they improve repeatability and supportability. D. Technical Strategy