I implement and maintain manufacturing execution systems.

For four years I've kept production running at Michelin — managing and deploying custom manufacturing execution software across three countries, forty Windows VMs, and eight production sites, on call around the clock. When a line goes down at a facility like that, the cost is real and the clock starts immediately. That environment shaped how I think about software: does it work when it has to?

Outside of work, I build things I wish existed. A travel app that predicts whether you'll get an upgrade based on your history. A dashboard that tells me when it actually makes sense to refinance. An eBay monitor so I stop overpaying for sports cards. None of it started as portfolio work — I just can't see a problem and leave it alone.

One night a database table quietly eclipsed its row limit and took a production line down. It took 24 hours to find and fix. The next thing I did was build a monitoring service that watched that table and sent an alert before it ever got close again. That's how I approach problems — fix it, then make it impossible to happen twice.

I'm not a developer by trade, but I ship software. I design the architecture, think through the problem, and use AI to close the gap between the idea and working code. I've outgrown a slow-moving environment and I'm looking for somewhere that moves fast, values that kind of thinking, and isn't afraid to put AI at the center of how they build.