Xealth · Seattle, WA

Salary
$150,000–$175,000from the description
Posted
Jul 13, 2026
Location
Seattle, WA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A data engineering role focused on designing and maintaining large-scale data pipelines, ingestion frameworks, and analytics infrastructure within a healthcare platform. The work involves distributed systems, cloud-native architecture on AWS, data lake management, and API integrations, translating clinical data into analytical datasets. Suited to engineers with at least three years of production experience in Python, SQL, and cloud-based data systems.

Mid level · 3+ years · Seattle-Tacoma-Bellevue, WA · Full-time

Must have (9)
PythonSQLDelta LakeApache ParquetApache AvroAWS, Azure or GCPKubernetesRESTIaC
Nice to have (5)
JavaScriptLLMsGitHub CopilotKafka or Flinkobservability

“or” means any one of them counts — you don't need all of them.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

Roughly 10 people in the Seattle-Tacoma-Bellevue, WA area plausibly meet what this posting asks for (database architects). range 4–15

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What gives you an edge
Apache Avro5%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
SQL90%Python55%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $107,748 (middle half $104,212–$164,448). This posting is about at that midpoint.

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (10)

The role sits at the boundary between data engineering (pipeline/warehouse building → 15-1243) and general software development (15-1252). The JD titles it 'software engineer on our data platform team' and emphasises CS fundamentals, clean architecture, and API design alongside data pipelines — hence the runner-up SOC.

The 3+ years requirement is stated at the role level ('3+ years building production software'), so it drives the overall years minimum rather than any individual skill.

Delta Lake, Parquet, and Avro appear in the Requirements section under 'Modern SQL and Non-SQL Database Design', making them hard gates. They also reappear under the Nice-to-Have section ('Data Systems Depth'), but their primary placement in Requirements governs.

AWS is named in the Requirements section alongside Kubernetes; 'or similar' is not stated, but alternatives are populated with the common peer cloud platforms a hiring manager would typically accept.

IaC is required by the 'Infrastructure as Code' bullet in the Requirements section; no specific tool (Terraform, Pulumi, CDK) is named, so no alternatives are listed.

JavaScript is explicitly called 'a plus' within the Requirements section itself — treated as preferred.

GitHub Copilot and Claude are mentioned in the Responsibilities section as examples of AI-assisted coding tools, not as gated requirements; they are listed as preferred. The Nice-to-Have section reinforces this for LLM/agentic experience.

Observability/monitoring/tracing appears only under the Nice-to-Have section.

The posting requires U.S. Citizenship or Permanent Residency — this cannot be represented in the schema fields but is a notable hiring constraint.

This is a hybrid role requiring in-office presence in Seattle; remote is set to false.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗