Practice
Principal architecture engagements focused on software platforms and business infrastructure.
Engagement Model
I work on a limited number of engagements at any given time, focused on building software platforms and business infrastructure where scale, complexity, or ambition are central concerns.
The work spans both design and implementation—bringing platforms from concept to market and shaping infrastructure that allows organizations to operate coherently as they grow.
Where I'm Useful
This work tends to be most effective in environments that value clear ownership and trust. I operate best when given agency over a defined system or surface area, with well-articulated goals and constraints.
I'm often brought in at one of two moments: as a founding developer when an ambitious idea needs to be designed to scale from launch, or as a rescue operator when a product or business begins to strain under growth.
I work collaboratively at the system level, integrating feedback from product, operations, and other stakeholders across the organization. I tend—though not exclusively—to thrive in startups and small teams, where there is sufficient latitude to design and build.
The strongest outcomes occur when the problem is real, the ambition is high, and the mandate is clear enough to move decisively without unnecessary friction.
Engagement Structure
Engagements vary in form. I've worked as a principal contributor, an embedded architect, and a technical lead depending on the nature of the work.
Structure, compensation, and duration are flexible — W2, 1099, or equity-based — determined by the alignment of incentives.
The questions that matter are simple:
Is the problem interesting? Is the ambition real? And could the work scale into something transformative?