Workplace
hybrid
Employment
Full-Time
Published
Feb 12, 2026
Closes
No date supplied
The role
WHY HARVEY At Harvey, we’re transforming how legal and professional services operate. By combining frontier agentic AI, an enterprise-grade platform, and deep domain expertise, we’re reshaping how critical knowledge work gets done for decades to come. This is a rare chance to help build a generational company at a true inflection point. We have strong product-market fit and world-class investor support. We’re scaling fast and defining a new category in real time. The work is ambitious, the bar is high, and the opportunity for growth — personal, professional, and financial — is unmatched. Our team moves fast, takes ownership, and is deeply committed to the mission — operating with intensity, staying close to our customers, and pushing each other for excellence. We live by three values: Decisiveness, Simplicity, and Job's Not Finished. We act quickly on clear judgment over perfect information, we believe simplicity is what scales, and we're never satisfied with where we are. If you want to do the best work of your career alongside people who share that drive, we'd love to build with you. At Harvey, the future of professional services is being written today — and we’re just getting started. ROLE OVERVIEW Harvey designs and builds for a legal industry being reshaped by AI, moving with the urgency and ambition the moment demands, not just adapting to change but architecting it. As a Design Systems Designer at Harvey, you will define the foundations that make our product coherent, scalable, and trustworthy as it grows in complexity. The design system is not just a library of components. It is the shared language between design, engineering, and AI that ensures consistency, quality, and confidence across every interaction. This is a design role with unusual technical depth. You lead with design: craft, systems thinking, and a strong point of view on product experience. But you're equally at home in architecture and implementation. You understand how tokens are structured,
Requirements
Department: Design; Team: Design