I build the systems that make operations run.

Most of these started as a problem nobody else was going to fix. I learned what was needed, built the fix, and shipped it into production. Everything below is real and running.

For the past eight years I have run the Amazon channel for a Canadian manufacturer, growing it from a small base into a channel doing several million annually. I own everything from listings and advertising to fulfillment operations and the reporting behind it.

Running that channel is where most of the systems above came from. When something manual, broken, or expensive showed up, I built the fix rather than waiting for someone else to. The channel funded the learning, and the learning kept compounding.

I started at this company on the warehouse floor. No degree, no bootcamp. I got here by taking on the next most obvious problem and refusing to leave it unsolved.

These days I build with AI tooling in the loop, which means I can prototype in a weekend what used to take a quarter. The judgment about what to build, how to integrate it, and whether it can be trusted in production is mine.

Working stack

I'm looking for automation and systems roles with companies that have more problems than builders. If your operations run on spreadsheets, tribal knowledge, and software that doesn't talk to each other, that's my home turf.