Source data from hospital systems is inconsistent and poorly documented. The contract has a hard end date, so scope discipline matters. Some pipelines run on a legacy orchestration tool being phased out mid-contract.
This is not a permanent role and there is no conversion guarantee. It is not a greenfield build — you are extending and stabilising an existing system. It is not an analytics or modelling role; the focus is pipelines and data quality.
A contractor who can ramp fast on an existing codebase, is comfortable owning a slice of the pipeline independently, and documents as they go so the permanent team can maintain it afterwards.
Take ownership of two existing pipelines and clear their backlog
Migrate one pipeline off the legacy orchestrator
Publish data-quality checks for the core operations dataset
This is a delivery-focused six-month contract. Most of the week is building and hardening batch and streaming pipelines in Python and SQL on a cloud data warehouse, plus backfilling historical hospital-operations data. Roughly one day a week is spent with the analytics team defining data contracts.
You work alongside two permanent data engineers and an analytics lead, reporting to the VP Data. Fully remote across US time zones, async-first with a daily written standup.
$170,000–$210,000 USD / year
Range as stated by the employer · USD · Annual
≈ $15,833.33 / month — derived from the stated annual range.
Clasva shows what an employer has and hasn't stated. Nothing here is inferred.
Ready to apply?
Apply on Meridian Health Systems's site