Back to jobs

Data Engineer - Healthcare

Pay
Pay not listedSimilar roles state $127K–$190K
Work setting
Working pattern needs review — work setting source
Location This role is not a remote position. You must be based in the United States and able to travel to the client site in Dover, Delaware as the project requires, including for design workshops and cutover windows. Travel is heaviest during Discovery and around production cutovers rather than on a fixed weekly pattern. How we work
Read the full posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full-time
From the employer’s posting

Before you apply

Eligibility
You must be based in the United States and able to travel to the client site in Dover, Delaware as the project requires, including for design workshops and cutover windows. — eligibility source
This role is not a remote position. You must be based in the United States and able to travel to the client site in Dover, Delaware as the project requires, including for design workshops and cutover windows. Travel is heaviest during Discovery and around production cutovers rather than on a fixed weekly pattern.
Read the full posting

What you’ll work on

Full posting

Delaware’s designated health information exchange and Health Data Utility is bringing its clinical data repository, its All Payer Claims Database and its internal warehouse onto one governed, longitudinal record.

You will own the pipelines and the migration waves that make this happen: building the ingestion and transformation layer for HL7 v2, C-CDA FHIR R4 and claims flat files, mapping them onto one health data ontology and proving - record by record - that what landed in the new platform matches what left the old one.

  • Build ingestion pipelines for HL7 v2, C-CDA, FHIR R4 and claims flat files

  • Map source records to a shared ontology aligned to FHIR R4 and US Core

  • Run migration waves with shadow loads, parallel runs and rollback plans

  • Build record-level reconciliation reports that gate each cutover

  • Produce per-sender data quality scorecards for source system owners

From the employer’s posting
Delaware’s designated health information exchange and Health Data Utility is bringing its clinical data repository, its All Payer Claims Database and its internal warehouse onto one governed, longitudinal record. Sand is delivering that platform on Symmetri, our data platform, running inside the client’s own AWS account.
You will own the pipelines and the migration waves that make this happen: building the ingestion and transformation layer for HL7 v2, C-CDA FHIR R4 and claims flat files, mapping them onto one health data ontology and proving - record by record - that what landed in the new platform matches what left the old one.
Design and operate pipelines for HL7 v2 (ADT, ORU, ORM, MDM, VXU), C-CDA, FHIR R4 and claims flat files
Transform records into shared objects — Person, Encounter, Condition, Result, Medication, Claim — aligned to FHIR R4 and US Core on the clinical side
Shadow load, parallel run, cutover with rollback, retire after acceptance.
Build the row-level and record-level reconciliation that compares counts, totals, identities and sampled clinical content between old and new.
produce six-dimension quality scorecards that go back to the source system owners

What you’ll bring

All qualifications

Core experience

  • 5+ years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership rather than project handover.
  • Proven experience migrating production data between platforms without interrupting live services — shadow loads, parallel runs, reconciliation and rehearsed rollback.
  • Experience with IHE profiles (XDS.b, XCA, PIX, PDQ) is a strong advantage.
  • Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code.
  • Experience building automated data quality frameworks, lineage capture and alerting as part of the pipeline, not bolted on afterwards.
  • Familiarity with clinical and claims terminology: ICD-10, CPT, LOINC, RxNorm, SNOMED CT, and value set management.
Qualification wording
5+ years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership rather than project handover.
Proven experience migrating production data between platforms without interrupting live services — shadow loads, parallel runs, reconciliation and rehearsed rollback.
Working knowledge of health interoperability standards — HL7 v2, C-CDA, FHIR R4 and US Core. Experience with IHE profiles (XDS.b, XCA, PIX, PDQ) is a strong advantage.
Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code.
Experience building automated data quality frameworks, lineage capture and alerting as part of the pipeline, not bolted on afterwards.
Familiarity with clinical and claims terminology: ICD-10, CPT, LOINC, RxNorm, SNOMED CT, and value set management.

About Sand Tech Holdings

From intelligent command centers to AI-powered infrastructure platforms, we help organizations sense, analyze and act in complex environments.

In the employer’s words · Read in context

Apply at Sand Tech Holdings

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 16, 2026today
Recorded sightings
1

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$190K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,380 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 6 and day 56.

At Sand Tech Holdings, jobs usually come down by about day 84.

From 13,890 similar postings that came down, and 8 of Sand Tech Holdings’s. Coming down is not always a hire.

Sand Tech Holdings is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Its jobs tend to stay up a long time
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • AWS
  • dbt
  • Kafka
  • Kubernetes
  • Spark
  • PySpark
Where the posting names them
- 5+ years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership rather than project handover. - Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code. - Deep hands-on expertise with distributed processing (Spark/PySpark) and streaming or event-driven systems (Kafka or equivalent).
About the role Delaware’s designated health information exchange and Health Data Utility is bringing its clinical data repository, its All Payer Claims Database and its internal warehouse onto one governed, longitudinal record. Sand is delivering that platform on Symmetri, our data platform, running inside the client’s own AWS account. The scale is real. The exchange has moved clinical data since 2007 and claims since 2013. It handles roughly 4.7 million HL7 messages and 220,000 CCDs a month from about 120 data senders, holds claims covering about 87% of Delawareans, and maintains around 5.5 million patient identities across 611 sources.
- Experience building lakehouse architectures on open table formats, with transactions, schema evolution and time travel. - Experience deploying and operating on AWS, including CI/CD and infrastructure-as-code. Kubernetes experience is valuable. - Demonstrated ability to design highly available, observable, production-grade data systems with defined SLAs and SLOs.
- Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code. - Deep hands-on expertise with distributed processing (Spark/PySpark) and streaming or event-driven systems (Kafka or equivalent). - Experience building lakehouse architectures on open table formats, with transactions, schema evolution and time travel.

Your next step

Complete your application on job-boards.eu.greenhouse.io. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 7% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 2. The fewest in a week was 861, the most 1,353, and the latest week had 1,335.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Job description

View original posting ↗

Data Engineer 

About Sand

Sand Technologies is a global Physical AI company using data and AI to make critical industries work better. We partner with governments, cities and enterprises to improve how essential systems operate across healthcare, water, energy, telecommunications and infrastructure.

Our work delivers proven real-world impact. We have built AI systems that help manage London’s water supply, supported telecom network planning across hundreds of cities, and developed digital healthcare platforms serving tens of millions of people across Africa. From intelligent command centers to AI-powered infrastructure platforms, we help organizations sense, analyze and act in complex environments.

Our people are ambitious, curious and relentlessly practical. Our teams work alongside clients in the field, solving hard problems and deploying solutions that last. With colleagues across Africa, Europe, the UK and the US, we operate across the full stack - from research and engineering to deployment and capability building.

Our mission is simple: to harness AI to solve humanity’s most pressing challenges.

About the role

Delaware’s designated health information exchange and Health Data Utility is bringing its clinical data repository, its All Payer Claims Database and its internal warehouse onto one governed, longitudinal record. Sand is delivering that platform on Symmetri, our data platform, running inside the client’s own AWS account.

The scale is real. The exchange has moved clinical data since 2007 and claims since 2013. It handles roughly 4.7 million HL7 messages and 220,000 CCDs a month from about 120 data senders, holds claims covering about 87% of Delawareans, and maintains around 5.5 million patient identities across 611 sources.

None of it can stop while we move it. Results delivery, admission alerts and state claims reporting run throughout. We migrate source by source, in parallel, with reconciliation the client can see and a rehearsed rollback on every cutover.

You will own the pipelines and the migration waves that make this happen: building the ingestion and transformation layer for HL7 v2, C-CDA FHIR R4 and claims flat files, mapping them onto one health data ontology and proving - record by record - that what landed in the new platform matches what left the old one.

We operate with a strong code-first, “data as a product” mindset, where testing, reliability, observability and performance are non-negotiables. In a regulated health environment with fixed federal funding deadlines, that discipline is the job, not a nice-to-have.

What you’ll do

  • Build the ingestion layer. Design and operate pipelines for HL7 v2 (ADT, ORU, ORM, MDM, VXU), C-CDA, FHIR R4 and claims flat files, parsing documents and messages into discrete, coded data elements rather than stored blobs.
  • Land everything raw and replayable. Every message and file is stored unchanged, time-stamped and re-runnable, with element-level provenance: source system, sender, received time, original message, pipeline and mapping version.
  • Map sources to one ontology. Transform records into shared objects — Person, Encounter, Condition, Result, Medication, Claim — aligned to FHIR R4 and US Core on the clinical side and the APCD Common Data Layout on the claims side. Map local codes to ICD-10, CPT, LOINC, RxNorm and SNOMED CT.
  • Run the migration waves. Shadow load, parallel run, cutover with rollback, retire after acceptance. Four waves across claims history, clinical history, live feeds and outbound consumers, each one signed off by the client before anything is switched off.
  • Prove the data moved correctly. Build the row-level and record-level reconciliation that compares counts, totals, identities and sampled clinical content between old and new. These reports are reviewed by the client's data quality staff and gate every cutover.
  • Make data quality measurable per sender. Validate structure, required fields, code validity, duplicates and volumes against each sender's baseline, and produce six-dimension quality scorecards that go back to the source system owners.
  • Engineer for failure. Every pipeline ships with retries, a dead-letter queue and a circuit breaker. A record that fails a quality check is never silently dropped — it goes to a steward, who fixes and replays it or discards it with an audit record.
  • Optimize what exists. Profile current pipelines for latency, failure rate, rejected messages and data quality, establish baselines, and rebuild them with validation at intake.
  • Write the data contracts. Every migrated dataset carries its schema, quality targets, owner, refresh schedule and consumers.

Who you are

Core engineering

  • 5+ years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership rather than project handover.
  • Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code.
  • Deep hands-on expertise with distributed processing (Spark/PySpark) and streaming or event-driven systems (Kafka or equivalent).
  • Experience building lakehouse architectures on open table formats, with transactions, schema evolution and time travel.
  • Experience deploying and operating on AWS, including CI/CD and infrastructure-as-code. Kubernetes experience is valuable.
  • Demonstrated ability to design highly available, observable, production-grade data systems with defined SLAs and SLOs.

Migration and data quality

  • Proven experience migrating production data between platforms without interrupting live services — shadow loads, parallel runs, reconciliation and rehearsed rollback.
  • Fluency in reconciliation technique: row counts, checksums, record-level comparison, and the judgement to know when a mismatch is a real defect rather than a modelling difference.
  • Experience building automated data quality frameworks, lineage capture and alerting as part of the pipeline, not bolted on afterwards.

Health data and regulated environments

  • Working knowledge of health interoperability standards — HL7 v2, C-CDA, FHIR R4 and US Core. Experience with IHE profiles (XDS.b, XCA, PIX, PDQ) is a strong advantage.
  • Familiarity with clinical and claims terminology: ICD-10, CPT, LOINC, RxNorm, SNOMED CT, and value set management.
  • Experience with healthcare claims data, ideally All Payer Claims Database work or the APCD Common Data Layout.
  • Experience building secure, governed data environments in regulated settings, with working knowledge of HIPAA and HITECH. Exposure to 42 CFR Part 2, Data Segmentation for Privacy (DS4P) or consent enforcement is highly valued.
  • Experience working with an enterprise master patient index and identity resolution. Verato, Mirth Connect or comparable integration engines are a plus.

How you operate

  • Comfortable in multi-stakeholder environments where a public agency, incumbent vendors, payers and more than a hundred data senders all have a say.
  • Systems-thinking mindset, focused on scalability, modularity and long-term platform evolution.
  • Able to work to hard external deadlines and acceptance gates without trading away test coverage or auditability.

We would rather hear from you than not. If you are strong on data engineering and migration but have not yet worked with health standards, say so and apply. Health interoperability is learnable by a good engineer; the migration discipline and the regulated-environment instincts are much harder to teach.

Location

This role is not a remote position. You must be based in the United States and able to travel to the client site in Dover, Delaware as the project requires, including for design workshops and cutover windows. Travel is heaviest during Discovery and around production cutovers rather than on a fixed weekly pattern.

How we work

Due to the highly collaborative and internationally distributed nature of our work, successful candidates must be comfortable operating in small teams while contributing to larger, globally coordinated efforts. A strong sense of ownership, self-motivation and discipline in maintaining clear and consistent communication through virtual collaboration tools and video conferencing is essential.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

USA

Core engineering - 5+ years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership rather than project handover. - Strong proficiency in Python and SQL, ideally with dbt, and a track record of clean, tested, production-quality code.
More source context
Location This role is not a remote position. You must be based in the United States and able to travel to the client site in Dover, Delaware as the project requires, including for design workshops and cutover windows. Travel is heaviest during Discovery and around production cutovers rather than on a fixed weekly pattern. How we work
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.