Healthcare Senior Data Engineer — Ingestion & Pipelines - Remote - Full-Time/Perm

Harvey Nash is hiring a Healthcare Senior Data Engineer to own protected health information pipelines and the data ingestion system. The role involves designing, building, operating, and improving patient-data pipelines, event-driven ingestion, recovery automation, observability, and governance across a healthcare data lakehouse environment.

Responsibilities:

• The primary responsibility for this position is to own the pipelines which touch protected health information (PHI). These are written in Python, using Ibis / DuckDB / Pandas, and run on Dagster as well as Kubernetes
• You will be the design owner for our PHI pipeline portfolio and for our data ingestion system, working within an architecture the CTO sets (lake layout, PHI segregation, orchestration patterns). You are being hired to make good engineering decisions inside a well-defended boundary, explain them clearly, get them reviewed, and ship them with strong and creative use of the Codex AI coding assistant
• You will also be the engineer of last resort for these pipelines. When a PHI pipeline fails at a moment that matters to a client, you are the person who answers
• Design, build, and operate the pipelines that handle identified patient data in Dagster on our DuckLake/Ibis/DuckDB lakehouse. This includes the patient-identity and record- linkage logic that determines whether a client’s data lines up correctly
• Own the ingestion lifecycle end to end: client submission through preprocessing, validation, enrichment, masking, and audit. Ingestion is event-driven on Azure Event Grid and Service Bus, and your job is to make it more stable, more observable, and more automated than it is today
• Our ingestion recovery and data movement are still partly manual. Turn them into fully idempotent, re-runnable, record-level-retryable processes with enterprise-grade observability and governance
• Every engineer here uses Codex, and the interview includes a live pairing session with your own tools
• You’ll work closely with the CTO and our other US engineers to keep refining how we do this
• For every system you list, we will ask why it was designed that way, what the alternatives were, and what you’d change now
• You’ll be working inside decisions you didn’t make and having your designs and code reviewed by people who did
• We ask for reliable availability by 8:00am Eastern for a few hours of daily overlap

Requirements:

• Healthcare data literacy (required). You have worked with patient-level data under HIPAA , and you know what an MRN, a registry, a quality measure, a benchmark, and a BAA are without being told
• Expert Python in production data systems
• Experience designing, building, and operating patient-data pipelines using a DuckLake/Ibis/DuckDB lakehouse
• Production SQL — you write it, tune it, and read query plans
• Deep experience with one modern orchestrator (Dagster, Airflow, Prefect, or similar) and the judgment to explain why it was the right choice and where it wasn't
• Ingestion lifecycle experience — File intake, validation, event-driven or queue-driven processing, failure handling and recovery, audit
• Kubernetes — you have deployed and operated workloads on it. You don't need to run the cluster but you know the difference between a node, an image, and a pod
• Observability instincts — you build things so that when they fail, you know, and you know why
• AI-assisted development practice with the discipline to own the output
• Sound engineering reasoning across the board — you can explain the tradeoffs behind every design decision you've made
• EMR/EHR integration: Epic, Cerner, Allscripts, HL7 v2/FHIR feeds at multi-hospital scale
• authorized to work in the US without sponsorship
• Clinical registry or quality-reporting experience: NCDR, STS, GWTG harvest data, risk models
• physician or service-line performance reporting
• Azure. DuckDB / Ibis. MySQL. Helm/Terraform
• Patient identity resolution / record linkage — if you've built it, we want to hear about it
• We do expect you to be the kind of engineer who has learned a new orchestrator and a new cloud before, and can tell us how it went
• Dagster is a big plus
• US citizens and Green Card Holders and those authorized to work in the US are encouraged to apply
• Eastern or Central time zone preferred. Will take PST candidates as well