Engineer in the system. Designer at the boundary.

My work crosses backend services, data pipelines, product interfaces, and operating doctrine. I am usually drawn to products where a clean happy path hides the real problem: missing evidence, provider failure, ambiguous identity, conflicting incentives, or complex human state.

I build across the whole loop when the work requires it. That has meant owning Go workers, Next.js applications, database contracts, API and MCP surfaces, product language, design systems, bot workflows, and the boring operational controls that keep a system credible after launch.

Writing, music, and visual work remain adjacent practices. They sharpen rhythm, composition, and the instinct to notice when an interface says more than its copy.