Data engineering · async, remote

Data pipelines that don’t break quietly.

A feed that failed three days ago and nobody noticed. A report the team has stopped trusting. A migration no one has validated.

I’m Will. I build and monitor the data pipelines behind clinical applications, and I prove the numbers are right — twelve years, nine of them at a 190-hospital system.

Start with a paid review. Read-only access, and in a few days you get a written scope: what’s wrong, what it takes to fix, what it costs. Yours to keep either way.

Email me the problem See the work
Async Fixed price You keep it
Will Jewell
About

Twelve years moving information between systems and checking it’s right — mostly where being wrong has real consequences.

Nine of those at HCA Healthcare — the largest hospital operator in the United States, around 190 hospitals — three in clinical analytics, then six building the data behind an app about 20,000 clinicians used every day, across 180+ hospitals and four record systems. When it broke, they knew within minutes — so I got good at building things that don’t break quietly. Degree from Georgia Tech.

I automate the repetitive part and do the rest by hand — what doesn’t resolve mechanically is what needs judgement. You own whatever I build: written down, running without me.

Outside work: being a dad, mostly — plus a Raspberry Pi I tinker with to make LEDs do fun things, and a community fridge I help keep stocked.
The practice

What I work on

Pipelines, monitoring and migration validation — mostly for teams whose data has consequences. Fixed price, agreed before I start: a $750 review first, builds $3,800–5,000, retainers from $3,000/mo. Full price list and terms →

Healthcare & clinical data →

Pipelines, data-quality monitoring and migration validation for healthcare and health-tech data teams.
→ Clinical data pipelines, monitoring and migration validation

Reference & write-ups

Reference notes

Specifics that are hard to find anywhere else.

  • How every engagement runs — Read-only access, what you own versus what I keep, response times, and liability — in plain English
Start asynchronously

Something in your data you don’t trust?

Email me the systems involved, what keeps breaking, and what the output should look like. I’ll reply with the first practical step and whether I’m a fit.

Email me the problem