Think from first principles
Challenge assumptions and understand the underlying problem before choosing a model, architecture, or workflow.
A hands-on engineer, technical founder, and senior technology leader who enjoys difficult questions—and is willing to challenge the assumptions behind them.
I’ve worked as a hands-on engineer, engineering director, Chief Architect, and founder. Before my current AI work, I helped build core functionality for Amazon EC2’s Elastic Load Balancing service. Today I’m the founder of ScaleReady, where I’ve led development of an AI-native platform for sales intelligence and customer engagement. That range lets me discuss product economics and technical strategy with leadership, then work directly with an engineering team on code, system design, model behavior, or a useful experiment.

The aim is a useful, dependable capability—not complexity for its own sake.
Challenge assumptions and understand the underlying problem before choosing a model, architecture, or workflow.
Stay close to implementation: write code, investigate failures, develop prototypes, and work alongside the people delivering the system.
Test what creates value. Sometimes an agent is the answer; sometimes a conventional workflow, a smaller model, or no AI at all is the better choice.
If you’re working on an AI-native product, an agentic workflow, or a new approach to software engineering, let’s discuss the problem and what success would look like.