About Me
I've always needed to see inside the machine.
When I encounter something new—whether it's a business model, a technical system, or a creative workflow—I tend to disappear for a while. I read, test, map constraints, break things, rebuild them. Only once I understand how something actually works do I feel comfortable using it.
That instinct has shaped my career and, increasingly, my life.
I've worked across sales, technology, operations, and venture-backed companies. In every role, the pattern was the same: step inside the system, understand how it runs, identify where it breaks, then help rebuild it so it works better. The domains changed, but the work didn't.
Over time, I realized I wasn't just collecting experience—I was collecting operating systems. Learning how organizations function from multiple vantage points: as an operator inside companies and as someone who understands how investors evaluate and support them.
Background (Briefly)
My career has spanned a mix of operating and analytical roles:
- IGN / Oracle — Learning sales systems under pressure
- Santa Clara University (MBA) — Pausing to retool
- Driscoll's — Understanding P&Ls and real-world economics
- Alexander Group — GTM strategy and operating frameworks
- Lyft — Scaling B2B inside a fast-growing platform
- Lightspeed — Building internal systems behind venture investing
Each stop was a new machine to understand.
A Change in Environment
In 2024, my wife and I made a deliberate decision to move our family to the Monterey Bay area, closer to where she grew up. It was a meaningful shift—one that reoriented how we think about time, community, and how we want to live.
That change created space to step back professionally as well.
I spent a period exploring entrepreneurship through acquisition as a way to pressure-test a long-held interest in ownership and end-to-end responsibility. While it ultimately wasn't the right long-term path, the process was valuable. It clarified how I like to work, what kind of problems energize me, and where I create the most leverage.
Going Deep on Systems
Alongside that exploration, I went deep technically.
I started building and running my own systems: Linux environments, Raspberry Pi–based services, automation pipelines, dashboards, and local tools that run continuously in the background. I learned by doing—setting things up, living with them, breaking them, and refining them until they were durable.
What surprised me was how much this work mirrored everything I'd done before.
My photography archive looks like a data system. My research workflows resemble ingestion pipelines. Dashboards are just interfaces. Hardware, software, files, APIs—it's all the same problem once you strip it down: how to design systems that are clear, resilient, and useful over time.
This site is where I document that work—not as polished case studies, but as a living record of how I think and build.
Now
I'm beginning a new professional chapter, bringing that systems-oriented way of working back into an organization. I'll write more about the "why" and "what" once it's underway.
Outside of work, I'm continuing to build and document personal infrastructure—tools, workflows, and environments that reflect a simple philosophy: use the right tool for the job, favor durable systems over convenience, and understand the machinery you depend on.
The through-line has never changed.
I fall asleep to How It's Made. Not out of boredom—out of peace. There's something grounding about watching a process unfold, step by step, until it works.
Most problems worth solving are systems problems.
That's what I enjoy working on.
→ try → learn → build → reflect → repeat