I've been a heavy Claude user since the API opened, drafting product specs in it, arguing with it about architecture decisions, occasionally letting it talk me down from a bad idea. So when I saw the Senior Product Designer job posting, I read it twice to make sure it wasn't a recruiting mirage.
What pulled me in was the framing of what does honest AI feel like in a chat surface as an open design question, not a settled one. For the last three years I've led end-to-end design on Claude-adjacent surfaces, most recently a workspaces beta that 18,000 users opted into in its first week. The work I'm proudest of has always lived at exactly that seam between trust and capability. Hard requirement · Lead a major surface
On mentorship: I've taken two designers from L4 to L5 and watched a design engineer become the most-asked-for collaborator on our team. Both took deliberate time. Both are part of why I keep coming back to roles like this one, the leverage of doing the work alongside people you're investing in. Responsibility · Mentorship
I also noticed the line about "we hire writers." I publish essays on design systems and AI surfaces (linked in my application). It's not a side practice for me, it's how I think through what I'm building, and the closest thing I have to a craft outside the product itself. Bonus · Writing practice
Two things I'd want to dig into in a conversation: how the design-system primitives hold up at the pace you ship, and what an honest team review looks like from the inside. Both are where I've done my best work. Looking forward to talking. Hard requirement · Design-system primitives