Back to jobs

Principal Database Reliability Engineer

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting
  • Define enterprise architecture principles anchored in OpenSearch and distributed systems

  • Resolve architecture conflicts across scalability, resilience, security, cost and lifecycle

  • Lead responses and systemic reviews for the most consequential multi-platform failures

  • Define strategy for shared Python automation platforms and Infrastructure as Code

  • Mentor Staff and Lead engineers and improve architecture-review decisions

From the employer’s posting
Define enterprise architecture principles and target-state direction anchored in OpenSearch and distributed-systems reliability.
Resolve architecture conflicts involving scalability, resilience, operability, security, cost, data movement, and lifecycle constraints.
Lead the technical response and systemic review for the most consequential multi-platform failures.
Define the strategy for shared Python automation platforms, operational APIs/CLIs, CI/CD guardrails, validation frameworks, safe remediation, and Infrastructure as Code.
Mentor Staff and Lead engineers, cultivate technical leadership, and improve architecture-review and decision-making quality.
Apply at Qualys

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 13, 202639 days ago
Recorded sightings
52
Last seen by us
Nov 15, 2026
Reposted
once since May 8, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications. We count a repost when the same title and location comes back as a new listing within 60 days of the last one coming down. Some hiring systems expire listings on a schedule, so repost rates vary by system.

How this job compares

Time since we first saw it

Day 39

Similar jobs usually come down between day 6 and day 56.

At Qualys, jobs usually come down by about day 53.

From 14,771 similar postings that came down, and 11 of Qualys’s. Coming down is not always a hire.

Qualys is hiring

11 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Data Engineer hiring has slowed
  • Takes jobs down at a usual pace
  • 9% of open jobs were reposted
Hiring record

See how this role fits your experience

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.

  • Python
  • ClickHouse
  • Elasticsearch
  • Kafka
  • Kubernetes
  • Oracle
  • PostgreSQL
  • Redis
Where the posting names them
C. Automation and Platform Engineering • Define the strategy for shared Python automation platforms, operational APIs/CLIs, CI/CD guardrails, validation frameworks, safe remediation, and Infrastructure as Code. • Promote self-service and platform-as-a-product practices that reduce toil while preserving change safety and accountability.
• Strong distributed-systems reasoning and meaningful production experience in at least two of Kafka, Redis, PostgreSQL, or Oracle. • Strong software-engineering and automation capability, preferably Python-based platform tooling and APIs. • Proven ability to define multi-year technical direction, resolve cross-domain architecture problems, and influence senior engineering and executive stakeholders.
• Kubernetes stateful platforms, cloud-managed data services, hybrid architectures, and Infrastructure as Code. • Experience with ClickHouse, Pinot, vector databases, NewSQL, stream processing, or similar emerging technologies. • Experience influencing vendors or open-source communities and guiding major modernization programs.
1. Role Summary We are seeking a hands-on Principal DBRE to serve as the highest individual-contributor technical authority for enterprise data-platform reliability and architecture. OpenSearch/Elasticsearch is the required anchor expertise. The role also requires strong breadth across distributed and relational data technologies, automation, observability, capacity, resilience, and technology strategy. The Principal DBRE defines multi-year direction, resolves consequential cross-domain architecture issues, establishes enterprise engineering principles, and influences senior engineering and executive leadership. The role guides domain specialists without requiring the individual to be the deepest expert in every database engine.
Anchor Technical Depth Serves as a recognized authority in OpenSearch/Elasticsearch and distributed-systems architecture, with enough depth to lead the most consequential technical decisions. Cross-Domain Breadth
• 12+ years of relevant database, DBRE, SRE, platform, or distributed-systems engineering experience with Principal, Staff, Lead, or comparable technical leadership responsibility. • Expert-level OpenSearch and/or Elasticsearch architecture and production operations experience. • Strong distributed-systems reasoning and meaningful production experience in at least two of Kafka, Redis, PostgreSQL, or Oracle.
Cross-Domain Breadth Demonstrates strong experience in at least two complementary domains such as Kafka, Redis, PostgreSQL, or Oracle, and can guide specialists across unfamiliar technologies. Strategic Leadership
• Expert-level OpenSearch and/or Elasticsearch architecture and production operations experience. • Strong distributed-systems reasoning and meaningful production experience in at least two of Kafka, Redis, PostgreSQL, or Oracle. • Strong software-engineering and automation capability, preferably Python-based platform tooling and APIs.
• Breadth across both distributed and relational database technologies. • Kubernetes stateful platforms, cloud-managed data services, hybrid architectures, and Infrastructure as Code. • Experience with ClickHouse, Pinot, vector databases, NewSQL, stream processing, or similar emerging technologies.

Your next step

Complete your application on qualys.wd5.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Has Qualys posted this job before?

Yes. We’ve followed one other Principal Database Reliability Engineer job there since May 2026. It came down after 118 days.

  1. PuneCame down after 118 days, first seen May 8
  2. This jobUp 40 days so far, first seen Oct 13

Job description

View original posting ↗

Come work at a place where innovation and teamwork come together to support the most exciting missions in the world!

Principal Database Reliability Engineer (DBRE) - Enterprise Data Platform

OpenSearch Anchor Expertise | Enterprise Architecture | Distributed Systems | Automation | Strategy

Level

Principal DBRE

Domain

Enterprise Data Infrastructure and Multi-Paradigm Data Platforms

Primary Focus

Enterprise technical direction anchored in OpenSearch, distributed-systems reliability, automation platforms, cross-domain architecture, and multi-year strategy

Work Expectations

U.S. Eastern Time business hours; on-call participation as required

 

1. Role Summary

We are seeking a hands-on Principal DBRE to serve as the highest individual-contributor technical authority for enterprise data-platform reliability and architecture. OpenSearch/Elasticsearch is the required anchor expertise. The role also requires strong breadth across distributed and relational data technologies, automation, observability, capacity, resilience, and technology strategy.

The Principal DBRE defines multi-year direction, resolves consequential cross-domain architecture issues, establishes enterprise engineering principles, and influences senior engineering and executive leadership. The role guides domain specialists without requiring the individual to be the deepest expert in every database engine.

2. Level Scope and Leadership Expectations

Principal DBRE is an executive-adjacent individual-contributor technical leadership role. The Principal establishes enterprise direction across multiple platform domains, resolves the most consequential architecture and reliability problems, and creates standards and investment priorities that scale across the organization.

Dimension

Expectation at This Level

Scope of Ownership

Shapes enterprise reliability, scalability, resilience, security, cost, and lifecycle direction across distributed and relational data-platform families.

Anchor Technical Depth

Serves as a recognized authority in OpenSearch/Elasticsearch and distributed-systems architecture, with enough depth to lead the most consequential technical decisions.

Cross-Domain Breadth

Demonstrates strong experience in at least two complementary domains such as Kafka, Redis, PostgreSQL, or Oracle, and can guide specialists across unfamiliar technologies.

Strategic Leadership

Defines multi-year architecture principles, technical roadmaps, production-readiness expectations, and investment priorities aligned with business needs.

Organizational Influence

Builds alignment across senior engineers, leaders, platform teams, and application organizations through clear tradeoffs, evidence, and measurable outcomes.

Platform Engineering

Champions reusable automation, observability, governance, and self-service capabilities as enterprise platform products.

 

3. Key Responsibilities

A. Enterprise Data-Platform Architecture

• Define enterprise architecture principles and target-state direction anchored in OpenSearch and distributed-systems reliability.

• Guide cross-domain decisions spanning search, streaming, caching, and relational services without displacing domain specialists.

• Resolve architecture conflicts involving scalability, resilience, operability, security, cost, data movement, and lifecycle constraints.

B. Reliability and Resilience Strategy

• Establish enterprise production-readiness, SLI/SLO, backup, recovery, DR, capacity, lifecycle, and incident-learning principles.

• Lead the technical response and systemic review for the most consequential multi-platform failures.

• Translate recurring incidents and platform risks into architecture safeguards and prioritized investment roadmaps.

C. Automation and Platform Engineering

• Define the strategy for shared Python automation platforms, operational APIs/CLIs, CI/CD guardrails, validation frameworks, safe remediation, and Infrastructure as Code.

• Promote self-service and platform-as-a-product practices that reduce toil while preserving change safety and accountability.

D. Technology Strategy and Organizational Influence

• Lead workload-relevant evaluation of emerging technologies, including operability, failure behavior, migration risk, performance, and total cost.

• Partner with senior engineering and executive leadership on multi-year technical direction, platform investments, and modernization decisions.

• Mentor Staff and Lead engineers, cultivate technical leadership, and improve architecture-review and decision-making quality.

4. Required Qualifications and Experience

• 12+ years of relevant database, DBRE, SRE, platform, or distributed-systems engineering experience with Principal, Staff, Lead, or comparable technical leadership responsibility.

• Expert-level OpenSearch and/or Elasticsearch architecture and production operations experience.

• Strong distributed-systems reasoning and meaningful production experience in at least two of Kafka, Redis, PostgreSQL, or Oracle.

• Strong software-engineering and automation capability, preferably Python-based platform tooling and APIs.

• Proven ability to define multi-year technical direction, resolve cross-domain architecture problems, and influence senior engineering and executive stakeholders.

• Deep understanding of reliability, capacity, observability, lifecycle management, DR, security, and cost tradeoffs.

• Excellent written communication, technical judgment, mentorship, and organizational influence.

5. Preferred Qualifications

• Breadth across both distributed and relational database technologies.

• Kubernetes stateful platforms, cloud-managed data services, hybrid architectures, and Infrastructure as Code.

• Experience with ClickHouse, Pinot, vector databases, NewSQL, stream processing, or similar emerging technologies.

• Experience influencing vendors or open-source communities and guiding major modernization programs.

6. Expected Outcomes in the First 6-12 Months

• Deliver an evidence-based enterprise data-platform architecture and reliability roadmap with clear priorities, ownership, and investment tradeoffs.

• Establish measurable baselines and lead material improvements in cross-platform reliability, MTTR, capacity risk, operational toil, and recovery readiness.

• Define and gain adoption of shared production-readiness, architecture-review, automation, and lifecycle-management principles.

• Guide at least one consequential platform modernization or technology decision from evaluation through an approved and supportable execution plan.

• Develop Staff and Lead technical leadership and improve cross-organizational architecture decision quality.

7. What This Role Does Not Include

• This is not a people-management role unless separately assigned.

• The Principal DBRE is not expected to be the deepest hands-on expert in every database technology; OpenSearch is the anchor expertise, supported by credible cross-domain breadth.

• This role does not replace Staff, Lead, or domain-specific subject-matter experts and operational owners.

• This role is not an executive approval authority; decisions are shaped through technical evidence, influence, and established governance.

• This role does not personally own every incident, implementation task, or operational detail; it focuses on the highest-impact cross-domain problems and systemic outcomes.

8. Work Expectations and Location

This role requires working during U.S. Eastern Time (ET) business hours and participating in on-call support as required.

About Qualys

People
About 2,625 in 2025, up 9% from the year before.Annual report (SEC Form 10-K)
Company
Listed as QLYS.
H-1B visas
21 approved for new hires in fiscal 2025.US Citizenship and Immigration Services

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

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.

About the role

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.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Pune

• Breadth across both distributed and relational database technologies. • Kubernetes stateful platforms, cloud-managed data services, hybrid architectures, and Infrastructure as Code. • Experience with ClickHouse, Pinot, vector databases, NewSQL, stream processing, or similar emerging technologies.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.