About

I'm a data engineer and architect. 12+ years working specifically with healthcare data, most recently Medicaid rate-setting, supplemental payment calculations and administration, and federal compliance demonstrations for state agencies, as a Managing Consultant at a large consulting firm. That depth is in the data, not the policy: I'm not the person who writes the regulation, I'm the person whose pipeline has to prove the state complied with it.

Underneath that specific expertise is 8 years building production data systems: data lakes, pipelines, cloud migrations, in Python, SQL, SAS, and Azure. That's the part that generalizes. A schema mistake or a broken pipeline has compliance consequences in this world, not just a bad dashboard, and I've come to think of that as the real training ground: the habits that hold up there hold up anywhere, regardless of industry.

I'm now transitioning from consulting into independent contract work. The engineering doesn't change: I'm still designing pipelines, running cloud migrations, and modeling data that has to be right the first time. What changes is who I build it for, and how directly.

Outside of client work, I build things because I want them to exist: a synthetic data generator, a self-hosted multiplayer game, a home automation stack that runs on the same instincts as everything else I build: contained, automated, and not held together with duct tape.