Hey! I'm Patri. I design for domains where the data is dense and the stakes are real, the kind of software where the interface is standing between someone and an answer they need now. Most of my last decade's experience has been in developer tooling and observability (think 3am, an alert just woke you up, and your site stopped responding for reasons), but the problem is the same anywhere experts work under pressure.
With 10+ years of product design experience, I work end to end: I start from the problem behind the feature request, get people aligned early, and design in systems so the work holds up as it scales. My background is in Design and Art History: two ways of asking how things are built, why they ended up that way, and how they're connected to the world… which is roughly how I ended up designing for engineers who live one layer below the interface. Learning a new domain is the part I enjoy most.
At New Relic I helped bring template variables to Dashboards and built a framework for custom visualizations; at Elastic I designed the log-processing workflows SREs lean on under pressure, and right now I'm working on a visualizer for managing data streams. The domain might change but the method doesn't: Every one of these started with me not understanding the users' work, and ended with me understanding it well enough to argue about it.
Currently, I use AI to prototype real interactions in Cursor (this site is one of them, shipped on Vercel) and to poke holes in my own thinking before a stakeholder has to.