About

I'm Owen. I work on the data-integrity side of pharmacy claims: platform migrations, reconciliation, and the incidents where the numbers stop agreeing. Claims are financial records in a regulated industry, so a wrong number here is a compliance problem rather than a failed test.

Before I wrote software for a living I spent years on the operations side of consumer finance, coaching teams and building the reporting that showed how the business was doing. That is where I learned what the numbers meant. The engineering came after: point of sale and checkout, then technical lead on payments at Indigo Tech Group, a Mindbody company (it has since been renamed Kite Technologies), working on the parts of a payment platform where compliance lives. Merchant onboarding, card-present processing, sanctions and beneficial-ownership screening, PCI.

The habit I care most about is keeping what the data proves apart from what it only suggests. I label an estimate as an estimate, I say when something hasn't been measured, and I correct my own findings before anyone acts on them. I've had to do that last one under real pressure.

I run my own infrastructure for related reasons. Photos, documents, passwords, books, and an offline copy of Wikipedia live on hardware I administer, behind a network I audit myself. Some of that is practical, but mostly I think people should be able to own their tools and their data, and I build that way.

I care about accessibility, because software that only works for some people is broken. I care about durability too: the best tools I use are decades old, and I'd like to build things that last that long.

Outside of work I play classical guitar, take long bike rides, travel, and cook for whoever shows up.