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.

I didn't take the straight path. Before I wrote software for a living I spent years on the operations side of consumer finance, first in dealership finance and insurance, then managing dealer performance across a territory, where I also built the reporting that told us how the business was actually doing. That is where I learned what the numbers meant. The engineering came after: consumer leasing systems at a fintech, point of sale and checkout, then technical lead on payments at Kite Technologies, formerly Indigo Tech Group, 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 separating what the data proves from what it suggests. In practice that means saying plainly what is still unmeasured, keeping a confirmed number apart from an estimated one, and correcting my own findings before they reach someone who will act on them. I have had to do all three under real pressure, and the last one is the part people remember.

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. Partly practicality, mostly principle: I think people should be able to own their tools and their data, and I build accordingly.

Two threads run through everything I make. Accessibility, because software that only works for some people is broken software. And durability, because the best tools I use are decades old and I would like to build things that earn that kind of lifespan.

Away from a keyboard: classical guitar, long bike rides, travel, and cooking for whoever shows up.