Consigue una respuesta de este empleador
Tu currículum y tu carta de presentación, adaptados exactamente a lo que buscan contratar.
Qualys in Pune, India, is seeking a Senior DBRE to improve reliability, performance, scalability, and automation for distributed data platforms. OpenSearch/Elasticsearch is the core technology, with production experience in Kafka and Redis, plus Linux systems, observability, and Python automation.
This is a hands-on, individual contributor role with on-call duties. You will own clusters, build automation, and contribute to platform design and production readiness while collaborating with SRE and
Come work at a place where innovation and teamwork come together to support the most exciting missions in the world!
Senior Database Reliability Engineer (DBRE) - Data Platform
OpenSearch Must-Have | Kafka | Redis | Python Automation | Production Reliability
Level
Senior DBRE (Senior Individual Contributor)
Domain
Distributed Data Infrastructure
Primary Focus
Hands-on reliability and operational ownership for assigned OpenSearch/Elasticsearch, Kafka, and Redis services; Python automation and disciplined production execution
Work Expectations
U.S. Eastern Time business hours; on-call participation as required
We are seeking an experienced Senior DBRE to improve the reliability, performance, scalability, and automation of mission-critical distributed data platforms. OpenSearch/Elasticsearch is the core must-have technology, complemented by production experience with Kafka, Redis, Linux systems, observability, and Python automation.
This is a hands-on role. The Senior DBRE independently operates assigned clusters and services, troubleshoots production issues, performs upgrades and lifecycle work, builds practical automation, and contributes to platform design and production-readiness standards.
The Senior DBRE is a high-impact hands-on engineer focused on independent execution within an assigned platform scope. Senior engineers solve common and moderately complex production problems, improve automation and runbooks, and contribute to designs and standards while escalating broader architectural decisions appropriately.
Expectation at This Level
Scope of Ownership
Owns assigned clusters, services, maintenance activities, incidents, upgrades, backup/restore, capacity reviews, and operational improvements with limited supervision.
Technical Depth
Diagnoses common and moderately complex issues involving shards, indexing, search, Kafka lag, Redis memory behavior, JVM, Linux, storage, and networking.
Automation
Builds and maintains tested Python tools, operational CLIs, API integrations, dashboards, alerts, and runbooks that reduce recurring toil.
Execution
Executes migrations, rolling upgrades, scaling, and DR exercises with change-management discipline and appropriate technical review.
Collaboration
Partners with Lead and Staff engineers, SRE, application, infrastructure, storage, network, and cloud teams; documents findings and communicates risks early.
Architecture Influence
Contributes evidence and operational experience to design reviews; does not independently set enterprise-wide platform architecture.
This is not a people-management role.
This is not passive monitoring, ticket routing, or a generic operations queue; hands-on troubleshooting and improvement are expected.
This role does not independently own enterprise-wide architecture or technical strategy.
This role does not own application code or product feature delivery, although close partnership with application teams is required.
The role does not require equal mastery of every listed platform; OpenSearch/Elasticsearch is the anchor expertise, with complementary Kafka and/or Redis depth.
This role requires working during U.S. Eastern Time (ET) business hours and participating in on-call support as required.