Products
Research the behavior. Find the real problem. Build the right first thing.
About
Engineer by training. Builder by instinct.
Systems / Product / Operations
My work has moved through healthcare, fintech, product, startups, live music, and food. On paper, those can look like different directions. To me, they are different versions of the same kind of problem.
I like figuring out how things work, where they break, and what needs to exist for them to work better.
I started with systems.
I earned both my bachelor's and master's degrees in Industrial and Systems Engineering at NC State, along with a minor in Statistics. I was drawn to problems with a lot of moving parts: processes, people, technology, constraints, and incentives. The interesting part was rarely optimizing one piece in isolation. It was understanding how the pieces affected each other.
My graduate work focused on Health Systems Engineering, where I applied that thinking to healthcare operations, including patient flow, capacity, and processes inside academic health systems. It showed me how much the design of a system can shape both the experience of the people inside it and the outcomes it produces.
That way of thinking stuck.
Then I started building them.
I carried that systems perspective into fintech, working on enterprise risk technology and helping scale a model execution platform across teams. It taught me what building inside a large organization actually requires: the technology can work and the system around it can still fail.
Adoption, governance, documentation, access, ownership, and operating processes matter just as much when something has to work beyond the team that built it.
Outside of work, I kept finding myself drawn to earlier-stage problems where more of the system was still undefined. That led me into building products, starting businesses, producing events, and helping turn ideas into things people could actually use, attend, or pay for.
Different outputs.
Same instinct.
Businesses
Figure out the economics, incentives, distribution, and operating model.
Systems
Make the work repeatable instead of solving the same problem twice.
Experiences
Create something people actually want to show up for.
The output changes. The way I approach the problem usually doesn't.
Outside the work
I've also spent a lot of my life doing things that have very little to do with sitting behind a desk.
I've competed in powerlifting at the national level, produced live events in New York and Dallas, traveled whenever I've had an excuse to, and somehow ended up deep in the food world without being able to cook.
I like bringing people together. A lot of what I build eventually comes back to that, whether it's a product, an event, a dinner, or something that doesn't have a name yet.
2×
National Powerlifting Champion
6×
National Record Holder
NYC → Dallas
Events produced
Always
Planning another trip
25 sec
Ideal microwave time for cookie dough
Closing thought
A lot of what I build comes back to creating spaces where people can come together, share something, and feel like they belong.
Sometimes that is software. Sometimes it is a business. Sometimes it is a room full of people.
I'm interested in what happens when you take an ambiguous idea seriously enough to make it real.