I've always been drawn to the part of engineering where the answer isn't obvious yet.
Give me a well-defined ticket and I'll build it. But the work I enjoy most starts earlier than that: a difficult problem, incomplete requirements, competing constraints, and a blank whiteboard. I like figuring out what the system should be before deciding how to build it.
Over the years, that's meant working across healthcare, autonomous vehicles, insurance, hospitality, blockchain, AI, and consumer software. Outside of my professional work, I've built my own products ranging from an AI-powered Bible platform to multiplayer games and experimental software ideas. The industries change, but the process is remarkably similar: understand the real problem, reduce the complexity, design the right system, and turn it into something people can actually use.
I tend to think beyond the feature directly in front of me. How should the data be modeled? Where are the boundaries in the system? What happens when this has ten times the traffic? How do we observe it in production? What happens when an API fails, the requirements change, or another engineer needs to understand this code a year from now? Good engineering isn't just making something work. It's making deliberate decisions about what deserves complexity and what doesn't.
That mindset also means I'm comfortable moving across the stack when the problem requires it. I might be working on an interaction in React or Flutter, tracing a request through an API, designing an event-driven workflow in GCP, investigating production telemetry, or figuring out where AI actually belongs in a product. I don't particularly care which layer owns the problem. I care about solving it well.
I'm also a relentless prototyper. Some ideas become production products. Some become experiments. Some probably should have stayed on the whiteboard. But building them has taught me something that years of working inside established systems can't: how to make decisions when there isn't already a roadmap, architecture, or team telling you what comes next.
After more than a decade of doing this, that's still the part of engineering I enjoy most.
Take something complicated, make it understandable, build it well, and ship something real.
Industries
- Healthcare
- ·Automotive
- ·Faith Tech
- ·Hospitality
- ·Blockchain
- ·AI
- ·SaaS
- ·Gaming
