Senior Staff Reliability Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes Company Description and Job Description. The "Job Description" includes "What You Get To Do In This Role" which is responsibilities. Then "Qualifications" section. There's also "Good To Have" which could be skills. There's also pay info: "For positions in this location, we offer a base pay of $190,900 - $334,100, plus equity (when applicable), variable/incentive compensation and benefits." Also benefits: "We also offer health plans, including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs." Also schedule? Not mentioned. So we can include Pay and Benefits sections. Also maybe "About the role" could be a short paragraph from company description? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. So we can have: - About the role: maybe a brief summary from job description: "Join us to build the next generation of cloud-native reliability, release, and test platforms..." That's specific. So we can put that as About the role. - Responsibilities: the bullet list under "What You Get To Do In This Role". Those are many lines; we need to put them as

• . - Requirements: maybe the qualifications? Actually Qualifications is separate. Requirements could be the mandatory qualifications (the "To be successful in this role you have:" list). That includes experience, education, etc. We'll treat that as Requirements. - Qualifications: maybe the "Good To Have" could be Skills? Or we could treat Qualifications as the mandatory qualifications and Skills as the "Good To Have". But the instruction lists both Qualifications and Skills as possible headings. We need to decide. The posting has "Qualifications" section (mandatory) and then "Good To Have". So we can map: - Qualifications: the mandatory list (experience, education, etc.) - Skills: the "Good To Have" list (observability, DevOps automation, etc.) - Benefits: the health plans etc. - Pay: the base pay range. - About the role: maybe the company description + job description intro? But we should not duplicate. We'll put a short paragraph summarizing the role: "Join us to build the next generation of cloud-native reliability, release, and test platforms that enable engineering excellence, developer productivity, and high-confidence ServiceNow releases through automation, observability, and AI-driven operations." - Responsibilities: the bullet list under "What You Get To Do In This Role". We need to omit boilerplate like Equal Opportunity Employer, Accommodations, Export Control Regulations, etc. Also omit "Additional Information Work Personas" etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as they appear (maybe rephrase? but must preserve detail). We'll copy them. We need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment:

  About the role

  Join us to build the next generation of cloud-native reliability, release, and test platforms that enable engineering excellence, developer productivity, and high-confidence ServiceNow releases through automation, observability, and AI-driven operations.

  Responsibilities

  • Design, build, and operate cloud-native engineering platforms for software validation, release validation, and production readiness
  • Design and maintain production-like release and test ServiceNow environments that improve release confidence and deployment readiness.
  • Build and integrate automated test pipelines, observability, reliability signals, deployment intelligence, and quality gates into CI/CD workflows.
  • Develop automation solutions that improve engineering productivity, streamline operations, and reduce manual toil through shift-left engineering practices.
  • Build reusable frameworks, self-service engineering environments, test data management, mock services, and developer productivity tooling.
  • Design and enhance Kubernetes-based platforms supporting scalable test infrastructure, release automation, cloud-native workloads, and developer self-service.
  • Implement automated validation for failure detection, deployment verification, policy enforcement, security checks, resilience testing, and operational health assessments.
  • Resolve complex platforms, infrastructure, and networking challenges through software engineering, systems design, and automation.
  • Partner closely with engineering teams to improve platform reliability, release quality, cloud-native adoption, and engineering best practices.
  • Participate in architecture reviews, technical design discussions, and implementation of scalable, automation-first engineering solutions.
  • Influence technical decisions through strong engineering execution, collaboration, and delivery of high-quality platform capabilities.
  • Mentor engineers through technical guidance, code reviews, knowledge sharing, and engineering best practices.
  • Foster a culture of reliability, automation, operational excellence, continuous improvement, and customer-focused engineering.

  Requirements

  • Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem‑solving. This may include using AI‑powered tools, automating workflows, analyzing AI‑driven insights, or exploring AI's potential impact on the function or industry.
  • 12+ years of experience in Site Reliability Engineering (SRE), DevOps, Platform Engineering, Software Engineering, or Infrastructure Engineering with a Bachelor's degree; or 8 years and a Master's degree; or a PhD with 5 years experience; or equivalent experience.
  • Hands‑on experience with Kubernetes across cluster operations, networking, storage, security, autoscaling, and multi‑cluster environments.
  • Experience building and operating cloud‑native platforms supporting scalable, highly available services.
  • Experience integrating Kubernetes with CI/CD, GitOps, automated test pipelines, deployment validation, and cloud‑native deployment workflows.
  • Experience designing and implementing automation to improve developer productivity, release quality, and operational efficiency.
  • Experience with progressive delivery practices, including canary deployments, feature flags, automated rollback, and deployment verification.
  • Experience with chaos engineering, resilience testing, disaster recovery, and reliability validation.
  • Strong software engineering skills with hands‑on experience designing, developing, testing, and debugging applications using Python, Go, Java, or Ruby.
  • Experience leveraging AI‑assisted engineering for intelligent testing, release risk analysis, incident diagnostics, or operational automation is a plus.
  • Strong understanding of observability, monitoring, SLI/SLOs, incident management, and production operations for distributed systems.
  • Demonstrated ability to solve complex technical problems, drive projects independently, and collaborate effectively across engineering teams.
  • Thrives in fast‑paced, ambiguous environments with a strong ownership mindset, bias for action, and a passion for continuous learning and automation.
  • Low ego, intellectually curious, and an effective collaborator who enjoys partnering with globally distributed teams to deliver reliable engineering solutions.

  Skills

  • Experience with observability and monitoring platforms for applications, services, and distributed systems at scale.
  • Experience with DevOps automation, CI/CD pipelines, GitOps, and Agile development practices using tools such as GitLab CI/CD, Argo CD, or Flux.
  • Experience building and maintaining enterprise‑scale test automation frameworks using technologies such as Playwright, Selenium, Cypress, REST Assured, PyTest, JUnit/TestNG, or equivalent.
  • Experience with test orchestration, intelligent regression testing, test impact analysis, flaky test detection, parallel execution, and test data management.
  • Experience with service virtualization, contract testing, synthetic testing, and building developer self‑service engineering platforms.
  • Experience with Infrastructure as Code and configuration management tools such as Ansible, Terraform, or equivalent.
  • Experience with the Kubernetes ecosystem, including Helm, Argo Workflows, Kustomize, Istio/Linkerd, Gateway API/Ingress, Prometheus, OpenTelemetry, and container runtime technologies.
  • Experience operating Kubernetes platforms across public cloud providers, including AWS (EKS), Azure (AKS), and Google Cloud (GKE).
  • Experience implementing progressive delivery practices, including canary deployments, feature flags, deployment verification, and automated rollback.
  • Familiarity with AI‑assisted engineering, intelligent testing, operational automation, or cloud‑native engineering platforms.

  Benefits

  • Health plans, including flexible spending accounts
  • 401(k) Plan with company match
  • ESPP
  • Matching donations
  • Flexible time away plan
  • Family leave programs

  Pay

  Base pay of $190,900 - $334,100, plus equity (when applicable), variable/incentive compensation and benefits.

  We should not include Schedule section because not present. Check that we didn't include any boilerplate. We omitted company description beyond the short paragraph? The company description at start: "It all started when engineer Fred Luddy..." That's substantive but maybe could be part of About the role? The instruction: About the role heading could be used for a summary of the role, not necessarily company description. But we could include company description as About the role? However we already used About the role for a short summary. The company description is also substantive; we could include it as a separate paragraph under About the role. But we must not invent or summarize away detail. We could add both: the company description paragraph and the role summary. But we must not repeat content. The company description is about ServiceNow; it's substantive. Should we include it? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid including company description under About the role. It says "About the role" as an example heading. So we could put the company description there. However we also have a role summary from job description. Could combine both. But we must not lose any substantive info. So we should include the company description paragraph as part of About the role. Let's include both paragraphs: first the company description, then the role summary. Or we could just put the company description as About the role and then the role summary as part of Responsibilities? But the role summary is not a responsibility; it's more of an overview. Better to put it under About the role. Thus About the role will contain two paragraphs: the company description and the role overview. Let's extract company description exactly: "It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people." We need to preserve that exactly. Then role overview: "Join us to build the next generation of cloud-native reliability, release, and test platforms that enable engineering excellence, developer productivity, and high-confidence ServiceNow releases