Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Senior Systems Engineer

Xealth
CompanyXealth
CategoryEngineering
LocationSeattle
RemoteOn-site (inferred)
EmploymentNot stated
LevelSenior
SalaryNot stated by the employer
Posted10 Jul 2026
Last verified4 Aug 2026
SourceEmployer ATS (greenhouse)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
Our Mission & Culture At Xealth, we’re revolutionizing healthcare by leveraging data and automation to empower care providers—building on EHRs such as Epic and Cerner—to seamlessly prescribe, deliver, and monitor digital health for patients. We are a detail-oriented team committed to maintaining high standards while moving with agility and impact. We are a highly skilled, collaborative, and passionate group, applying our expertise to improve health outcomes for millions. We believe in shared ownership and are looking for a team player who is a self-starter and self-driven to pioneer the next generation of intelligent, automated cloud infrastructure. The Role We're looking for a Senior Systems Engineer to take full ownership of our AWS EKS Kubernetes platform and the open source ecosystem that powers it. This is a hands-on, high-ownership role — you'll be the go-to expert for cluster reliability, observability, GitOps automation, and infrastructure-as-code. You'll work closely with our engineering teams to ensure our platform is resilient, secure, and continuously improving. This isn't a ticket-queue operations role. We want someone who thinks architecturally, automates relentlessly, and raises the bar for how we build and run infrastructure. *Must be open to working a hybrid schedule; in our office is in Seattle.*  What You'll Own EKS cluster platform — day-to-day operations, version lifecycle management, node group strategy, cluster upgrades, and capacity planning across environments GitOps delivery pipeline — own and evolve our ArgoCD-based deployment workflows, enforce GitOps patterns across teams, and drive consistency in how services reach production Observability stack — build and maintain our Prometheus/Grafana observability platform; define SLOs, alerting standards, and dashboards that give engineering teams actionable signal Infrastructure-as-code — manage and extend Terraform codebases for AWS infrastructure; enforce IaC standards and participate in code review OpenTelemetry instrumentation — lead the adoption and standardization of OTel across services for distributed tracing, metrics, and log correlation Linux systems health — own OS-level configuration, hardening, patching, and performance tuning across our compute fleet Security & compliance posture — partner with engineering and security to enforce least-privilege IAM, secrets management, network policies, and audit readiness in a HIPAA-regulated environment What We're Looking For Required 5–8 years of hands-on systems/platform engineering experience Deep Kubernetes expertise — you can reason about scheduling, networking, storage, RBAC, and cluster internals without reaching for the docs Production experience running workloads on AWS EKS Strong Linux fundamentals — systemd, networking, kernel tuning, troubleshooting under pressure Proficiency with Terraform for AWS infrastructure management Hands-on experience with ArgoCD or Flux in a production GitOps workflow Experience building and operating Prometheus/Grafana observability stacks Working knowledge of OpenTelemetry — collectors, instrumentation libraries, pipeline configuration Programming and scripting experience with Python,Typescript, Bash Comfort operating in a regulated environment (HIPAA, SOC 2, or similar) Nice to Have Experience with service mesh (Linkerd, Istio, or similar) Familiarity with Kafka in a Kubernetes context Secrets management experience (AWS Secrets Manager, or External Secrets Operator) Prior work at a healthcare or health-tech company Contributions to open source projects How We Work Hybrid in Seattle — we value in-person collaboration and flexibility in equal measure Infrastructure managed as code — if it's not in Git, it doesn't exist On-call expectations are reasonable and shared across the team You'll have real autonomy