Data Engineer - Healthcare

Sand Tech Holdings Limited
•Onsite

About The Position

Sand Technologies is hiring a Data Engineer to build and operate the data pipelines and migration waves for Delaware’s designated health information exchange and Health Data Utility. The project brings the client’s clinical data repository, All Payer Claims Database, and internal warehouse together into a governed longitudinal record on Sand’s Symmetri data platform, running in the client’s AWS account. The migration must preserve ongoing services, including results delivery, admission alerts, and state claims reporting. The role covers ingestion and transformation of HL7 v2, C-CDA, FHIR R4, and claims flat files; mapping records to a shared health data ontology; and proving, record by record, that migrated data matches the source. Work proceeds through shadow loads, parallel runs, cutovers with rehearsed rollback, and retirement after client acceptance. The engineer will also implement measurable data-quality controls, reconciliation, observability, failure handling, and data contracts. The position follows a code-first, “data as a product” approach in a regulated health environment with fixed federal funding deadlines. It requires close collaboration with a public agency, incumbent vendors, payers, data senders, and distributed teams. This is not a remote position: the employee must be based in the United States and able to travel to the client site in Dover, Delaware as project needs require.

Requirements

  • At least 5 years designing and operating large-scale data platforms in cloud or hybrid environments, with production ownership.
  • Strong proficiency in Python and SQL; a track record of clean, tested, production-quality code.
  • Hands-on expertise with distributed processing such as Spark/PySpark and streaming or event-driven systems such as Kafka or equivalent.
  • Experience building lakehouse architectures on open table formats, including transactions, schema evolution, and time travel.
  • Experience deploying and operating on AWS, including CI/CD and infrastructure-as-code.
  • Ability to design highly available, observable, production-grade data systems with defined SLAs and SLOs.
  • Proven experience migrating production data between platforms without interrupting live services, including shadow loads, parallel runs, reconciliation, and rehearsed rollback.
  • Fluency in reconciliation techniques such as row counts, checksums, and record-level comparison, with the judgment to distinguish defects from modeling differences.
  • Experience building automated data-quality frameworks, lineage capture, and alerting as part of data pipelines.
  • Working knowledge of health interoperability standards: HL7 v2, C-CDA, FHIR R4, and US Core.
  • Familiarity with clinical and claims terminology, including ICD-10, CPT, LOINC, RxNorm, SNOMED CT, and value set management.
  • Experience with healthcare claims data.
  • Experience building secure, governed data environments in regulated settings, with working knowledge of HIPAA and HITECH.
  • Experience working with an enterprise master patient index and identity resolution.
  • Comfort working in multi-stakeholder environments involving public agencies, incumbent vendors, payers, and numerous data senders.
  • Systems-thinking mindset focused on scalability, modularity, and long-term platform evolution.
  • Ability to meet external deadlines and acceptance gates without compromising test coverage or auditability.
  • Must be based in the United States and able to travel to the client site in Dover, Delaware as project requirements dictate.
  • Comfort operating in small teams and contributing to globally coordinated efforts, with ownership, self-motivation, discipline, and clear communication through virtual collaboration tools and video conferencing.

Nice To Haves

  • Experience with dbt.
  • Kubernetes experience.
  • Experience with IHE profiles such as XDS.b, XCA, PIX, or PDQ.
  • Experience with All Payer Claims Database work or the APCD Common Data Layout.
  • Exposure to 42 CFR Part 2, Data Segmentation for Privacy (DS4P), or consent enforcement.
  • Experience with Verato, Mirth Connect, or comparable integration engines.

Responsibilities

  • Design and operate ingestion pipelines for HL7 v2 message types (ADT, ORU, ORM, MDM, VXU), C-CDA, FHIR R4, and claims flat files, parsing them into discrete coded data elements.
  • Store every message and file unchanged, timestamped, replayable, and with element-level provenance, including source, sender, received time, original message, pipeline, and mapping version.
  • Transform data into shared objects such as Person, Encounter, Condition, Result, Medication, and Claim, aligned with FHIR R4 and US Core for clinical data and the APCD Common Data Layout for claims.
  • Map local codes to ICD-10, CPT, LOINC, RxNorm, and SNOMED CT.
  • Run migration waves using shadow loads, parallel runs, cutover with rollback, and retirement after acceptance; obtain client sign-off before switching off existing systems.
  • Build row-level and record-level reconciliation comparing counts, totals, identities, and sampled clinical content between old and new platforms.
  • Validate each sender’s structure, required fields, code validity, duplicates, and volumes against baselines, and produce six-dimension quality scorecards for source system owners.
  • Build pipeline failure handling, including retries, dead-letter queues, and circuit breakers; route records failing quality checks to a steward for correction and replay or audited discard.
  • Profile current pipelines for latency, failure rate, rejected messages, and data quality; establish baselines and rebuild pipelines with validation at intake.
  • Define data contracts for each migrated dataset, including schema, quality targets, owner, refresh schedule, and consumers.
  • Maintain testing, reliability, observability, performance, auditability, and production ownership of data systems.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service