👨‍💻 I'm a software engineer working at WAI!, and we are building the team and culture needed to achieve our ambitious goal–to become the leader in AI security and safety.

Most of my work starts where the answer is not obvious.

The goal may be unclear. The boundary may be wrong. Ownership may not match authority. A dependency may control the critical path. Or a system may work only because someone keeps the right context in their head.

I like taking those situations and making them actionable — first by creating enough clarity to move, then by looking for what can be turned into a boundary, contract, tool, workflow, or mechanism so the next person does not have to reconstruct the same judgment from scratch.

That has taken my work across product engineering, architecture, developer platforms, AI and agentic systems, engineering productivity, and organizational design. I’m less interested in where a problem sits in the stack than in what has to change for the system to work better.

A simple model I keep coming back to is:

Turn ambiguity into actionable clarity.
Turn repeated judgment into mechanism.
Ask: why does this still require me?