Senior Staff Software Engineer - Data Platform - Kubernetes - Distributed Systems - Federal

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About The Team, What You Get To Do In This Role, Qualifications, It Also Helps If You Have..., For positions in this location, we offer a base pay..., We also offer health plans..., Additional Information (but we should drop boilerplate like EEO, legal, etc). We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - Position Location: Flexible (Hybrid) position. This is location info, maybe part of "Schedule"? Actually schedule is about work arrangement. Could be "Schedule" heading. But we only include sections when posting has real specific content. The posting says: "Position Location: This is a Flexible (Hybrid) position. Flexible positions require 2 days per week in a ServiceNow office location. We have offices in several locations, including San Francisco, CA; Pleasanton, CA; Santa Clara, CA; San Diego, CA; and Kirkland, WA". That's schedule/location info. Could be under "Schedule". We'll include a

Schedule

with that info in

or

. Probably

. - About The Team: we can treat as "About the role" maybe. Or "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map sections accordingly. We have "About The Team" description: "We are seeking a Senior Staff Software Engineer (IC5 Level) to join our Data Platform Engineering organization. You will be a hands-on technical lead who will lead the design and delivery of shared, multi-tenant platform services — Postgres, queueing/streaming, and key-value stores — on Kubernetes, and serves as the technical anchor for their availability, resilience, and operating model." That's more about the role/team. Could go under "About the role". We'll put that. Then "What You Get To Do In This Role": list of responsibilities. That's responsibilities. So

Responsibilities

with
• items. Then "Qualifications": list of qualifications. That's qualifications. So

  Qualifications

  with
  . Then "It Also Helps If You Have": that's additional preferred qualifications/skills. Could go under "Skills". So

  Skills

  with
  . Then "For positions in this location, we offer a base pay of $149,800 - $262,200, plus equity (when applicable), variable/incentive compensation and benefits." That's pay and benefits. We have separate headings for Pay and Benefits. The posting mentions base pay range, equity, variable/incentive compensation and benefits. Then later: "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." That's benefits details. Thus we can have

  Pay

  with base pay range and equity/variable compensation. And

  Benefits

  with health plans etc. We should not include sections like "Schedule" if we already used location info maybe under Schedule. But we already have location info; we could put under Schedule. However we also have Pay and Benefits sections. The instruction says prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for About the role, Responsibilities, Qualifications, Skills, Pay, Benefits, Schedule (location). That's many sections but each is substantive. Could we combine Pay and Benefits? The instruction says use headings like Pay, Benefits separately. So we should keep them separate. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove "Additional Information Work Personas ..." etc. Also remove "Equal Opportunity Employer", "Accommodations", "Export Control Regulations", "From Fortune." etc. We must preserve all substantive information. Ensure we don't lose any detail. Let's extract details: Company Description: Not needed for job posting? It's part of description but not required to be a section. Could be included as a paragraph before sections? The instruction: "Preserve ALL substantive information". So we need to include company description somewhere. It's not a heading; we can put it as a

  before sections. Job Description: Position Location details. About The Team. What You Get To Do In This Role. Qualifications. It Also Helps If You Have. For positions in this location, we offer a base pay... We also offer health plans... We should also include the note about base pay being a guideline etc. That's part of Pay. Also note: "Compensation is based on the geographic location in which the role is located and is subject to change based on work location." Include. Now produce HTML. Structure:

  Company description paragraph(s).

  Schedule

  Position Location: This is a Flexible (Hybrid) position. Flexible positions require 2 days per week in a ServiceNow office location. We have offices in several locations, including San Francisco, CA; Pleasanton, CA; Santa Clara, CA; San Diego, CA; and Kirkland, WA.

  About the role

  We are seeking a Senior Staff Software Engineer (IC5 Level) to join our Data Platform Engineering organization. You will be a hands-on technical lead who will lead the design and delivery of shared, multi-tenant platform services — Postgres, queueing/streaming, and key-value stores — on Kubernetes, and serves as the technical anchor for their availability, resilience, and operating model.

  Responsibilities

  • Lead the design and delivery of shared platform services — managed Postgres, queueing/streaming, and key-value/cache — that run on Kubernetes across a large global fleet and that product teams across the company depend on, owning them from design through production operation.
  • Act as the technical lead on major initiatives within your team, breaking down ambiguous problems — “offer HA Postgres as a service to every cluster,” “make our queueing tier survive a zone loss” — into clear, executable designs with explicit availability, durability, and cost targets.
  • Define the HA, failover, disaster-recovery, and multi-region architecture for the services you own, and the Kubernetes-native automation (operators, controllers, CRDs, self-service APIs) that provisions, scales, upgrades, and fails them over without human intervention.
  • Partner with principal and distinguished engineers to align your work with the broader platform architecture and standards, and with product teams to set consumption contracts, tenancy models, and SLOs for shared services.
  • Identify technical risks early and drive them to resolution, with a strong focus on reliability, scalability, and operability — leading failure-mode analysis, game days, and post-incident reviews for stateful systems.
  • Spend significant time hands-on — designing, coding, and reviewing the core systems your team builds, such as operators, controllers, infrastructure automation, and platform services.
  • Mentor mid-level and junior engineers and raise the engineering bar through code reviews, design feedback, and pairing — particularly around distributed-systems and data-service design.

  Qualifications

  • Experience leveraging or critically thinking about how to integrate AI into engineering and platform work — whether using AI-powered tooling, automating operational workflows, building agentic systems for fleet visibility and operations, or reasoning about AI’s impact on how infrastructure is built and run.
  • 12+ years of software development experience with a Bachelor's degree; OR 8+ years with a Master's degree; OR 5+ years with a PhD; OR equivalent work experience.
  • 8+ years building production software, with solid experience operating distributed systems and running stateful workloads on Kubernetes at scale.
  • A track record of leading the design and delivery of at least one shared, multi-tenant infrastructure service used broadly by other teams — a relational database service (Postgres or similar), a message queue or streaming platform (Kafka, NATS, RabbitMQ, or similar), or a key-value/cache service (Redis/Valkey, etcd, or similar) — including its HA, failover, and operating model.
  • Deep understanding of high availability and failure handling: replication topologies, leader election, quorum and consensus, split-brain avoidance, backup/restore and point-in-time recovery, and designing to explicit RPO/RTO and durability targets.
  • Strong system design skills — you can reason rigorously about consistency models, partitioning and rebalancing, capacity planning, tenant isolation, and noisy-neighbor mitigation, and communicate the trade-offs clearly to engineers and stakeholders.
  • Hands-on experience with at least one major hyperscaler (AWS, Azure, GCP), including its core compute, networking, storage, and IAM primitives.
  • Strong working knowledge of containers and Kubernetes (including stateful primitives: StatefulSets, CSI/persistent storage, PDBs, topology spread), CI/CD and GitOps-based delivery, and infrastructure-as-code.
  • Strong programming skills in Go (or strong systems-language skills with a willingness to work primarily in Go).

  Skills

  • Experience building or extending Kubernetes operators that manage stateful systems (e.g., CloudNativePG, Zalando/Crunchy Postgres operators, Strimzi, Redis/Valkey operators), and opinions on when to adopt versus build.
  • Deep expertise in one of the target systems: Postgres internals (WAL, streaming/logical replication, vacuum, connection pooling with PgBouncer/PgCat, major-version upgrades); Kafka/NATS (partitioning, ISR/replication, exactly-once semantics, consumer scaling); or Redis/Valkey (cluster mode, persistence, eviction, hot-key handling).
  • Experience running data services across multiple regions or clusters — cross-region replication, failover orchestration, and DR testing.
  • Experience with zero-downtime upgrades, schema/data migrations, and fleet-wide rollouts of stateful services.
  • Experience with observability and SLOs for stateful systems — replication lag, saturation, tail latency, error budgets — and with capacity and cost management for shared infrastructure.
  • Experience designing multi-tenancy: quotas, isolation, chargeback/showback, and self-service provisioning APIs or CRDs.
  • Experience with container networking (CNI) and/or service mesh, and with workload identity, mTLS, and secrets management as applied to data services.
  • Experience with managed Kubernetes (EKS/AKS/GKE), managed data services (RDS/Aurora, Cloud SQL, MSK, ElastiCache), and infrastructure-as-code tools such as Terraform or Crossplane.

  Pay

  For positions in this location, we offer a base pay of $149,800 - $262,200, plus equity (when applicable), variable/incentive compensation and benefits. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location. Compensation is based on the geographic location in which the role is located and is subject to change based on work location.

  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.

  We should ensure