Here to turn ideas into products.
Product designer, former front-end engineer. Figma and a code editor, usually open at the same time.
Currently @ Microsoft
Designer who prototypes
In React as well as Figma, wired to real APIs rather than mock data — so a direction meets real latency and real content before anyone builds it. I prototype with agentic tooling too, mostly to find my own weakest assumption before a critique does.
Systems, not screens
I gravitate to the parts of a product everyone touches and nobody owns: design libraries, deprecated components, the states nobody drew.
Complex domains
SharePoint, Office.com, Windows, Copilot — expert users, dense data, and rendering decisions that are fine at a hundred rows and broken at ten thousand.
The designer who reads the pull request.
Five years of front-end across SharePoint, Office.com, Windows and Copilot, then a deliberate move into design. Recent work includes M365 Companions and M365 Copilot.
How I work with others
Design doesn't happen alone. What each team can expect when we're working together.
- With Engineering
- I spent five years as the engineer on the other side of the handoff, so I share rough work before it is polished and write functional documentation a build can actually run on.
- With Product
- I push for clarity on success measures upfront and challenge scope while it is still cheap to change — then commit fully to the problem we agreed on.
- With Research
- Research is not a service I order: data insight analysis sits inside my own process, and what it turns up changes what I design rather than confirming it.
- With Other Designers
- I give specific, actionable critique and expect the same back, mentor early-career designers and engineers, and turn what I work out into a template or guide the team can reuse.