About

While I was at Michigan I turned a laptop-review side project into a real business. Laptologist drove a few million in sales over its run, and almost none of the work was code: it was writing, SEO, analytics, and paying contributors.

It was fun for a while, until I slowly grew tired of the affiliate-marketing world. But it taught me how a business actually works, and that still shapes how I think about software.

Livegistics is where I really learned to build and ship software with a team: a greenfield platform for construction managers, a React Native app for the drivers, and all the data plumbing between them.

It was the first time I owned code that people depended on every day, and I loved it.

At Trajector I worked across internal platforms, document-processing pipelines, cross-team integrations, and later some AI-assisted QA tooling. The platform we built went from an MVP to something an operations team lived in every day.

I got promoted to senior there, and somewhere along the way built the first EventBridge pattern that a lot of other teams ended up adopting.

After Trajector I packed up for a ten-week AI engineering fellowship at Gauntlet in Austin. It was intense in the best way. Most of my time went into evals and a kids' learning app that ran computer vision right on the device.

Then I moved to LA for Cover. They design and build houses on a factory line and truck them across Southern California, closer to manufacturing than construction, which I find genuinely fascinating. I work on the software behind that pipeline, and I'm still pretty new.