I design enterprise software for technical people.

I'm a Product Designer with a background in frontend engineering, so I think about implementation as much as I think about the interface.

I work on search, data exploration, observability and developer workflows. It's software where the interface has to earn a technical user's trust before it earns their time, so I get close to the data model and the query language, not just the screens on top of them. Right now, that's Discover at Elastic.

Good enterprise software starts with understanding the domain, not the screen. I work closely with Product Management, Engineering, and the users and customers who'll actually live in what we build, from discovery through delivery: prototyping early, testing often with users and SREs, and staying involved long enough to see whether a decision actually held up in production.

AI is part of how I work now, not a separate step. I use it to synthesise research, draft copy, prototype in code, and explore directions I wouldn't otherwise have time for. It hasn't replaced the thinking. It's just given me more time to do it.