Make it clear
I started in design and web, learning how people understand products and how good interfaces remove friction.
ABOUT
Builder with range.
Operator with judgment.
I have spent more than two decades in environments where clarity is limited, speed matters and execution decides what survives.
THE THROUGH-LINE
I do not separate technology from the business it has to move.
My work has crossed design, growth, software engineering, architecture, AI, product and technical leadership. That range is not a collection of unrelated chapters. It is how I learned to see the whole system.
The strongest technical decision often starts somewhere outside the codebase: the user problem, the economics, the operating constraint, the speed of the market or the consequence of being wrong. I like the point where those realities meet engineering.
THE EVOLUTION
Make it perform
Growth, analytics and lifecycle systems made the work measurable. Product decisions became acquisition, retention and revenue outcomes.
Make it scale
Engineering, architecture, infrastructure and data became the focus as the products, traffic, costs and consequences grew.
Lead the whole system
CTO-level roles expanded the problem again: teams, product judgment, technical strategy, economics, risk and execution under pressure.
Stay close to the work
Today I am hands-on in engineering again while operating across growth and technical strategy. The perspective compounds rather than resets.
TODAY
Hands-on engineering. Broader operating context.
My current role puts me directly in the work: engineering systems, applying AI, improving infrastructure and solving product problems. It also extends into growth and technical strategy.
I see that as continuity. CTO-level experience changed the way I build; being close to the implementation keeps strategy grounded. Each side makes the other better.
See the career trajectory →OPERATING PRINCIPLE
“The job is not to make the architecture impressive. The job is to make the system work.”