Product Designer

<div class="content-intro"><p><span style="font-size: 12pt;"><strong>About DevRev</strong></span></p> <p>At DevRev, we're building the future of work with <em>Computer</em> – your AI teammate. Unlike traditional tools, <em>Computer</em> unifies all your data sources, tools, and workflows into a single AI-ready platform, giving employees real-time insights, proactive suggestions, and powerful agentic actions. It extends your existing software with AI-native apps and agents that work alongside your teams and customers – updating workflows, coordinating across teams, and eliminating repetitive work. We call this Team Intelligence: human-AI collaboration that breaks down silos, brings people back together, and frees you to solve bigger problems. Backed by Khosla Ventures and Mayfield with $150M+ raised, DevRev is trusted by global companies across industries.</p></div><p><strong>About the role</strong></p> <div> <p>At this level, you're no longer just contributing - you're driving. You own complex product areas, raise the quality of work around you, and operate with significant autonomy. You're producing judgment: making hard trade-offs, owning them, and explaining what you sacrificed and why. At DevRev, this means designing the communication layer of an AI-native platform - the surfaces where humans and Computer exchange meaning, where conversations carry consequence, and where the difference between a chatbot and a teammate lives in the details of interaction.</p> <p>Messages is foundational infrastructure. Every product team at DevRev depends on the patterns you establish here. You'll define how conversations begin, evolve, interrupt, resume, and resolve - across threads, channels, real-time exchanges, and async flows. This isn't feature work; it's the connective tissue of the entire platform.<strong>&nbsp;</strong></p> </div> <div><strong>What you'll do</strong> <div> <ul> <li>Own the end-to-end design of messaging experiences across DevRev - from real-time conversation flows to asynchronous threads, notifications, and presence.</li> <li>Define interaction patterns for human-to-human, human-to-Computer, and Computer-initiated communication that feel native to each context.</li> <li>Make hard trade-offs between information density, interruptibility, and conversational flow - and articulate what you sacrificed and why.</li> <li>Design for progressive disclosure and graceful complexity: messages carry metadata, context, actions, and links to the knowledge graph without overwhelming the reader.</li> <li>Collaborate closely with engineering on the technical constraints of real-time systems - latency, optimistic UI, delivery states, and platform adaptation.</li> <li>Contribute to Arcade (our design system) at the pattern level - your messaging components become the reference implementation other teams build on.</li> <li>Mentor L1-L3 designers with enough structure that they grow visibly; give feedback that demonstrably improves work.</li> </ul> </div> <div><strong>What you'll bring</strong> <div> <ul> <li>5-8 years of product design experience.</li> <li>Expert-level proficiency with Figma and prototyping tools.</li> <li>Deep understanding of conversational interfaces, messaging systems, or real-time collaboration products.</li> <li>Demonstrated ability to own outcomes, not just outputs - you can point to a behaviour that changed or a metric that moved because of a decision you made.</li> <li>Experience designing interactions that handle real-world complexity: progressive disclosure, interruptibility, optimistic UI, error recovery.</li> <li>Strong systems thinking - you consider downstream consumers, systemic coherence, and long-term durability alongside immediate quality.</li> <li>Excellent communication skills; when you disagree with a product decision, you bring an alternative with evidence, not just an objection.</li> </ul> <h3>Who you are</h3> <ul> <li>You're driven by design excellence and produce judgment others reference.</li> <li>You don't optimize for comfort - you optimize for the user, even when that's the harder engineering path.</li> <li>You navigate ambiguity by reframing problems before opening Figma.</li> <li>The people around you do better work because of the quality of your feedback.</li> <li>You think at the system level: before finishing any component, you can name three other contexts it will appear in.</li> </ul> <p>&nbsp;</p> </div> </div> </div><div class="content-conclusion"><p><em>DevRev is an equal opportunity employer and does not discriminate on the basis of race, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition, or any other basis protected by law.</em></p></div>