Skip to content

About

I work best on ambiguous technical problems that sit across product, platform, and organizational boundaries.

Over time I've gravitated toward the kinds of problems that don't have a clean handoff line: global customer-facing architecture, performance work that spans many teams, platform decisions that shape how organizations build, and AI systems that need to be useful under real production constraints.

What I do best

  • Define technical direction for customer-facing systems
  • Improve org-level leverage through platform and performance mechanisms
  • Build architecture that survives scale and delegation
  • Align multiple teams without direct authority
  • Turn high-ambiguity spaces into executable technical strategy

Operating principles

  1. Start with constraints, not solution fashion
  2. Build mechanisms that survive delegation
  3. Instrument before optimizing
  4. Reduce complexity across boundaries, not just inside one team
  5. Treat AI as a systems problem, not a demo

Background

My path into engineering didn't start in computer science. I studied exercise physiology, where I spent four years studying how the human body maintains homeostasis across dozens of interconnected systems (cardiovascular, respiratory, nervous, endocrine) all coordinating under constantly changing conditions.

That background shaped how I approach software. I reason from constraints and first principles rather than pattern-matching to textbook solutions. When I encounter a performance problem, I start by observing the system's actual behavior, the same scientific method I learned in a physiology lab. When I think about failure modes, I think about cascading failures the way a physiologist thinks about how one organ's dysfunction propagates through the whole body.

From physiology I moved into startups, building full-stack products from zero across healthcare and fintech. Those years taught me the visceral connection between engineering quality and business outcomes. Then six years at Amazon (AWS IoT, QuickSight, and Project Kuiper) where the problems grew to organizational scale and the systems became genuinely distributed.

What I'm looking for

I'm most interested in Staff, Principal, and Senior Staff roles where the core challenge is not just building software, but defining how complex software gets built across teams.

Open to remote, Seattle/Bellevue-based, or relocation to Europe.