About

I'm a data engineer and architect. Eight years building production data systems — data lakes, pipelines, cloud migrations — and twelve-plus years working specifically with claims and risk data, most recently as a Managing Consultant at a large consulting firm.

That work has mostly landed in regulated industries — healthcare and government — not because I set out to specialize there, but because that's where the highest-stakes data problems tend to live. Systems where a schema mistake or a broken pipeline has compliance consequences, not just a bad dashboard. I've come to think of that as the real training ground: the habits that hold up there hold up anywhere.

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.