Senior or Product Designer, Design Systems

Harvey is building AI-first products for the legal and professional services sector and is hiring a Senior or Staff Product Designer focused on Design Systems. The role involves defining and implementing the foundations that make the product coherent, scalable, and trustworthy as it grows in complexity and will report to the Design org. The position will be based in San Francisco, New York City, or Toronto.

The company emphasizes building an AI-native design system and collaboration between design, engineering, and product.

• Design, prototype, and ship production-ready system components in tight collaboration with frontend and platform engineering, with shared ownership of quality, performance, and maintainability
• Define and evolve core design system foundations (components, patterns, and tokens) that scale across complex, AI-powered experiences
• Push both the architecture and the implementation of the system: shape component APIs, token structure, theming, and composition patterns alongside engineering
• Advocate for technical approaches in new or ambiguous territory where established patterns don't yet exist
• Embed accessibility, responsiveness, and performance into the system by default
• Establish clear contribution, governance, and deprecation models that balance velocity with system integrity
• Raise the bar for system quality across the product through design reviews, critique, and hands-on work
• Build alignment across Design, Engineering, and Product through technical direction and collaboration

• 5+ years (Senior) or 8+ years (Staff) of product design experience with significant ownership of design systems in complex product environments
• A design portfolio demonstrating high design craft, system-level thinking, a strong point of view on quality, and visual cohesion
• Deep design systems expertise, including understanding the history and evolution of the discipline
• Excellent design-engineering communication and the ability to clearly articulate system decisions and tradeoffs to designers, engineers, and cross-functional partners
• Strong knowledge of scalable system architecture and component implementation, including component API design, design tokens, theming strategies, and how systems hold up across teams and codebases
• Design Engineer experience preferred but not required
• High ownership: treating the system as a product rather than a ticket queue
• Strong opinions, loosely held, and comfort challenging conventions and evolving best practices