ABOUT

I fell in love with design before I could write code.

By junior year of high school, I was spending half my day at a vocational center doing technical drafting — the kind where you draw by hand, think in systems, and care about precision. I placed third nationally my senior year. What drafting taught me wasn't a skill. It was a way of seeing: everything you build is a decision, and every decision has consequences downstream.

WHERE IT STARTED 1991 - 1996

My first job out of college was at System Sensor Division — a commercial smoke detector company. I was laying out PCBs when I realized we needed software to extract drill location data from the board files for manufacturers. I wrote it. Nobody asked me to. That moment — realizing I could build a tool that solved a real problem and nobody was going to stop me — that's when the career actually started.

THE ISR ERA 1996 - 2002

Wireless home control before smartphones. Voice activation before Alexa. Whole-home audio three years before Sonos. A home automation platform deployed in the homes of Michael Dell, Wayne Huizenga Jr., and Frank Thomas.

We weren't ahead of the curve. We were the curve.

Bill Gates spent the night at Michael Dell's house and told him our system was more capable than his own. I was six years into my software development career.

NUCLEAR INFRASTRUCTURE 2003 - PRESENT

Then I went to build something harder. Twenty years of 24/7 mission-critical software for US nuclear power plants. Two $1B+ acquisitions. Recruited back twice. Promoted three times. Today, across all products, we hold over 60% market penetration across the US nuclear fleet.

I held a Secret security clearance (DOD) and spent two decades in air-gapped, NRC-regulated environments where uptime is a legal requirement, not a marketing claim. That background shapes how I think about reliability, architecture, and what it means for software to actually work.

THE AI CHAPTER 2024 - PRESENT

I've spent the last year building Camino — a spec-driven development system that brings engineering discipline to AI-assisted software delivery. On my own time, I'm architecting a multi-agent AI system modeled after a holding-company hierarchy. I'm not just using AI. I'm building with it.

That's the problem I'm solving now: AI is only as useful as the system you build around it. Anyone can prompt. Not everyone can be an architect.

PHILOSOPHY

Teams built on trust consistently outperform teams built on process. I've seen it across five companies, two acquisitions, and thirty years. The best engineering I've been part of happened when people felt safe enough to say "I don't know."

The technology changes. The instinct doesn't.

WHAT I'M LOOKING FOR

I'm looking for a founder who knows the difference between a team that ships fast and a team that ships well — and wants both. Small enough that what I build matters, actually. Ambitious enough that the problems are worth solving.
I'm not looking for a title. I'm looking for a place where engineering discipline is a competitive advantage, not a bureaucratic obstacle — and where the person at the top understands why that distinction matters.

See my work
"I'm not searching for any opportunity. I'm looking for the right one."
Let's talk