Time since we first saw it
Day 44
Similar jobs usually come down between day 6 and day 56.
At Qualys, jobs usually come down by about day 53.
From 14,767 similar postings that came down, and 11 of Qualys’s. Coming down is not always a hire.
Employment type in the employer’s posting: Full timeFrom the employer’s posting
Operate and scale assigned OpenSearch/Elasticsearch clusters, including shard and indexing troubleshooting
Operate Kafka topics, consumer groups, and brokers; diagnose lag and rebalance issues
Operate Redis Cluster and Sentinel environments, handling memory, replication, and failover issues
Build and maintain tested Python automation for health checks, maintenance, and remediation
Execute upgrades, migrations, scaling, and DR exercises with change-management discipline
Operate, scale, and improve assigned OpenSearch/Elasticsearch clusters and node topologies.
Operate Kafka topics, partitions, replication, retention, consumer groups, and broker health; diagnose lag, rebalance storms, and capacity bottlenecks.
Operate Redis Cluster and Sentinel environments; address memory fragmentation, eviction behavior, persistence, replication lag, connection limits, and failover issues.
Develop clean, modular Python automation for health checks, maintenance, validation, reporting, and safe remediation.
Executes migrations, rolling upgrades, scaling, and DR exercises with change-management discipline and appropriate technical review.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 44
Similar jobs usually come down between day 6 and day 56.
At Qualys, jobs usually come down by about day 53.
From 14,767 similar postings that came down, and 11 of Qualys’s. Coming down is not always a hire.
11 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
Senior Database Reliability Engineer (DBRE) - Data Platform OpenSearch Must-Have | Kafka | Redis | Python Automation | Production Reliability Level
Primary Focus Hands-on reliability and operational ownership for assigned OpenSearch/Elasticsearch, Kafka, and Redis services; Python automation and disciplined production execution Work Expectations
1. Role Summary 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.
Automation Builds and maintains tested Python tools, operational CLIs, API integrations, dashboards, alerts, and runbooks that reduce recurring toil. Execution
C. Automation and Infrastructure as Code • Develop clean, modular Python automation for health checks, maintenance, validation, reporting, and safe remediation. • Use Terraform, Ansible, GitOps workflows, or Kubernetes operators where applicable to make platform operations repeatable.
• Strong Linux and systems troubleshooting skills across CPU, memory, storage I/O, networking, and process behavior. • Ability to write maintainable Python automation beyond simple one-off shell scripts. • Experience with monitoring, incident response, controlled production changes, upgrades, and operational documentation.
• Establish measurable baselines and deliver material improvements in reliability, alert quality, MTTR, and recurring operational toil for assigned services. • Automate high-frequency maintenance and validation workflows using maintainable Python tooling. • Improve runbook coverage, upgrade readiness, backup/restore confidence, and capacity visibility.
• Terraform, Ansible, GitOps, Kubernetes, ECK/OpenSearch, Strimzi, or Redis operators. • Cloud-managed data services in AWS, Azure, or GCP. • Familiarity with ClickHouse, Pinot, vector databases, Flink, Spark Streaming, or Kafka Connect.
• Cloud-managed data services in AWS, Azure, or GCP. • Familiarity with ClickHouse, Pinot, vector databases, Flink, Spark Streaming, or Kafka Connect. 6. Expected Outcomes in the First 6-12 Months
3. Key Responsibilities A. OpenSearch and Elasticsearch Operations • Operate, scale, and improve assigned OpenSearch/Elasticsearch clusters and node topologies.
A. OpenSearch and Elasticsearch Operations • Operate, scale, and improve assigned OpenSearch/Elasticsearch clusters and node topologies. • Troubleshoot shard allocation, indexing throughput, slow search and aggregation workloads, cluster state, JVM heap/GC, disk, memory, and recovery issues.
• 5+ years of relevant DBRE, SRE, database, or distributed-systems operations experience in production environments. • Strong hands-on OpenSearch and/or Elasticsearch experience, including shards, indexing, search, lifecycle management, JVM behavior, and snapshot/restore. • Production experience with at least one of Kafka or Redis; experience with both is strongly preferred.
• 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. 8. Work Expectations and Location
D. Reliability and Incident Response • Instrument actionable metrics and alerts using Prometheus, Grafana, OpenTelemetry, or comparable platforms. • Participate in on-call, stabilize incidents, document root cause, and complete preventive actions.
Technical Depth Diagnoses common and moderately complex issues involving shards, indexing, search, Kafka lag, Redis memory behavior, JVM, Linux, storage, and networking. Automation
• Implement and maintain index templates, shard strategies, ISM/ILM policies, rollover, retention, snapshot, restore, and rolling-upgrade procedures. B. Kafka and Redis Operations • Operate Kafka topics, partitions, replication, retention, consumer groups, and broker health; diagnose lag, rebalance storms, and capacity bottlenecks.
B. Kafka and Redis Operations • Operate Kafka topics, partitions, replication, retention, consumer groups, and broker health; diagnose lag, rebalance storms, and capacity bottlenecks. • Operate Redis Cluster and Sentinel environments; address memory fragmentation, eviction behavior, persistence, replication lag, connection limits, and failover issues.
• Strong hands-on OpenSearch and/or Elasticsearch experience, including shards, indexing, search, lifecycle management, JVM behavior, and snapshot/restore. • Production experience with at least one of Kafka or Redis; experience with both is strongly preferred. • Strong Linux and systems troubleshooting skills across CPU, memory, storage I/O, networking, and process behavior.
5. Preferred Qualifications • Hands-on experience with both Kafka and Redis. • Terraform, Ansible, GitOps, Kubernetes, ECK/OpenSearch, Strimzi, or Redis operators.
• Develop clean, modular Python automation for health checks, maintenance, validation, reporting, and safe remediation. • Use Terraform, Ansible, GitOps workflows, or Kubernetes operators where applicable to make platform operations repeatable. D. Reliability and Incident Response
• Hands-on experience with both Kafka and Redis. • Terraform, Ansible, GitOps, Kubernetes, ECK/OpenSearch, Strimzi, or Redis operators. • Cloud-managed data services in AWS, Azure, or GCP.
• Operate Kafka topics, partitions, replication, retention, consumer groups, and broker health; diagnose lag, rebalance storms, and capacity bottlenecks. • Operate Redis Cluster and Sentinel environments; address memory fragmentation, eviction behavior, persistence, replication lag, connection limits, and failover issues. C. Automation and Infrastructure as Code
Complete your application on qualys.wd5.myworkdayjobs.com. The employer’s form will show what is required.
Already applied? Track this application
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
1. Role Summary
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.
3. Key Responsibilities
• Operate, scale, and improve assigned OpenSearch/Elasticsearch clusters and node topologies.
• Troubleshoot shard allocation, indexing throughput, slow search and aggregation workloads, cluster state, JVM heap/GC, disk, memory, and recovery issues.
• Implement and maintain index templates, shard strategies, ISM/ILM policies, rollover, retention, snapshot, restore, and rolling-upgrade procedures.
• Operate Kafka topics, partitions, replication, retention, consumer groups, and broker health; diagnose lag, rebalance storms, and capacity bottlenecks.
• Operate Redis Cluster and Sentinel environments; address memory fragmentation, eviction behavior, persistence, replication lag, connection limits, and failover issues.
• Develop clean, modular Python automation for health checks, maintenance, validation, reporting, and safe remediation.
• Use Terraform, Ansible, GitOps workflows, or Kubernetes operators where applicable to make platform operations repeatable.
• Instrument actionable metrics and alerts using Prometheus, Grafana, OpenTelemetry, or comparable platforms.
• Participate in on-call, stabilize incidents, document root cause, and complete preventive actions.
• Contribute to capacity planning, production-readiness reviews, runbooks, and design reviews.
• 5+ years of relevant DBRE, SRE, database, or distributed-systems operations experience in production environments.
• Strong hands-on OpenSearch and/or Elasticsearch experience, including shards, indexing, search, lifecycle management, JVM behavior, and snapshot/restore.
• Production experience with at least one of Kafka or Redis; experience with both is strongly preferred.
• Strong Linux and systems troubleshooting skills across CPU, memory, storage I/O, networking, and process behavior.
• Ability to write maintainable Python automation beyond simple one-off shell scripts.
• Experience with monitoring, incident response, controlled production changes, upgrades, and operational documentation.
• Clear communication, sound judgment, and willingness to escalate risk early.
• Hands-on experience with both Kafka and Redis.
• Terraform, Ansible, GitOps, Kubernetes, ECK/OpenSearch, Strimzi, or Redis operators.
• Cloud-managed data services in AWS, Azure, or GCP.
• Familiarity with ClickHouse, Pinot, vector databases, Flink, Spark Streaming, or Kafka Connect.
• Establish measurable baselines and deliver material improvements in reliability, alert quality, MTTR, and recurring operational toil for assigned services.
• Automate high-frequency maintenance and validation workflows using maintainable Python tooling.
• Improve runbook coverage, upgrade readiness, backup/restore confidence, and capacity visibility.
• Contribute a well-supported evaluation or operational-readiness recommendation for one relevant emerging technology when business needs require it.
• 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.
8. Work Expectations and LocationThis role requires working during U.S. Eastern Time (ET) business hours and participating in on-call support as required.
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Pune
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.