Product Designer

About the role Youll define the design infrastructure that every product team at DevRev builds on. Where L4 designers own specific product areas, your work is more structural: evolving Arcade (our design system), defining global interaction patterns, building design tooling, and ensuring that foundational decisions compound across the platform rather than fragment. Youre part designer, part design engineer - someone who thinks architecturally and isnt afraid to get into code, prototyping environments, or toolchain automation to make the whole team faster and more consistent. What youll do Shape Arcades architectural evolution - identifying when the system cant support new needs and proposing solutions that maintain coherence. Define global patterns that multiple product teams adopt: layout systems, responsive behaviour, data display conventions, navigation structures. Build and maintain design tooling - Figma plugins, prototyping infrastructure, token pipelines, documentation systems - that accelerate the work of others. Prototype at the systems level to de-risk architectural decisions before theyre expensive to reverse. Pioneer interaction patterns for Computers conversational paradigm - designing for the edge cases that separate a teammate from a chatbot. Set production standards that hold without your direct involvement: documented, replicable, and enforced through process rather than vigilance. Develop designers through structured critique - building conditions where good work is the natural output. What youll bring 8-10 years of product design experience. Design engineering sensibility: comfort working across Figma, code (CSS/JS/React or equivalent), and token-based systems. You dont need to be a full-stack engineer, but you think in implementation terms and can build what you design. Architectural understanding of design systems - not just component libraries but token structures, contribution models, versioning, and governance. Experience defining standards that other designers and engineers adopt and maintain independently. Strong prototyping skills at the systems level, not just the feature level. Ability to identify when three teams are solving the same problem differently and propose the unified framework. Who you are When theres a design disagreement, people look to you - not because of title but because your reasoning is consistently the most sound. You define what great looks like, not just produce it. Your standards outlast your direct involvement. You think in systems and build in systems - the gap between your Figma file, your prototype, and the shipped product is negligible because you designed with implementation in mind from the start. Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.