Senior Systems Engineer

How to use this kit

Ground every answer in facts on this page and the original listing. We never invent Glassdoor-style reviews or salaries that are not in our data.

Occupation tasks (O*NET)

Public-domain labor data — prepare examples for 2–3 of these.

• Propose logistics solutions for customers.
• Develop logistic metrics, internal analysis tools, or key performance indicators for business units.
• Conduct logistics studies or analyses, such as time studies, zero-base analyses, rate analyses, network analyses, flow-path analyses, or supply chain analyses.
• Identify cost-reduction or process-improvement logistic opportunities.
• Review contractual commitments, customer specifications, or related information to determine logistics or support requirements.
• Evaluate effectiveness of current or future logistical processes.
• Prepare logistic strategies or conceptual designs for production facilities.
• Provide logistics technology or information for effective and efficient support of product, equipment, or system manufacturing or service.

O*NET source

Company facts (cached)

Website: xealth.com

Public cache only — not an employee review.

Role overview (listing rewrite)

Senior Systems Engineer at Xealth in Seattle, WA—architect and operate the cloud infrastructure powering digital health at scale. In this full-time, hybrid role, you'll take complete ownership of our Kubernetes platform, working closely with engineering teams to ensure our systems are resilient, secure, and continuously improving. About the Role We're seeking an engineer who owns infrastructure end-to-end: from cluster lifecycle management to observability frameworks, GitOps delivery pipelines, and infrastructure-as-code. This is not a reactive support function—you'll make architectural decisions, eliminate manual toil through automation, and set the technical bar for how we design and operate our platform. You'll be the domain expert on cluster health, infrastructure patterns, and operational discipline, working with product engineers to ensure our platform scales reliably in a healthcare environment governed by HIPAA and SOC 2 compliance requirements. Core Duties Manage AWS EKS cluster platform operations, including version lifecycle, node capacity strategy, cluster upgrades, and performance optimization across all environments Build and maintain our ArgoCD-based GitOps delivery architecture; establish GitOps patterns and ensure services reach production through consistent, auditable workflows Own our observability infrastructure built on Prometheus and Grafana; define SLO frameworks, alerting policies, and dashboards that provide engineering teams with actionable insights Develop and extend Terraform-based infrastructure definitions for AWS resources; review IaC patterns and enforce standardization across the organization Lead OpenTelemetry adoption and standardization across services, enabling distributed tracing, unified metrics, and log correlation Administer Linux systems configuration, hardening, patching workflows, and performance tuning across our compute nodes Partner with security and engineering teams to implement least-privilege IAM policies, secrets management, network segmentation, and compliance audit preparation Requirements 5 to 8 years of hands-on systems and platform engineering experience Deep expertise in Kubernetes—confident reasoning about scheduling, networking, storage, role-based access control, and cluster internals Demonstrated production experience running workloads on AWS EKS Strong Linux fundamentals including systemd, network configuration, kernel tuning, and troubleshooting Proficiency writing Terraform code for AWS infrastructure provisioning and management Production experience with ArgoCD or Flux in a GitOps workflow Hands-on experience building and operating Prometheus and Grafana stacks Working knowledge of OpenTelemetry components, instrumentation, and pipeline configuration Programming and scripting…

Full job on Get A Job.AI

Questions to ask them

• What does success look like in the first 90 days for this role?
• How is the team structured, and who would I work with most?
• What tools and systems does this role use daily?
• Is the work primarily based in Seattle, WA , hybrid, or fully remote?