Design Systems Lead

About Ramp Ramp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a business spends. We automate how over $200B in annualized spend flows in and out of 70,000+ companies: authorizing payments, flagging risk, categorizing spend, and closing books. The problems are high-stakes, data-dense, and unforgiving. We hire people with high agency and high urgency. We look for slope over intercept. We care less about where you trained and more about what you’ve built. At Ramp, everyone is a builder who owns problems end to end and makes consequential decisions that shape the outcome. The median Ramp customer saves 5% and grows revenue 16% in their first year – far in excess of businesses operating without Ramp. We believe every ambitious company deserves the same. If you want to build systems that directly shape how companies move and manage billions, Ramp is the place to do it. About the Role How we build software is changing. Designers are building tools and agents, prototyping in code, and shipping directly into the product. More people can create software than ever before. That makes design judgment more important, not less. We’re looking for a Design Systems Lead to build that judgment into the foundations of Ramp. This is not just about maintaining a component library. It’s about making it possible for designers, engineers, and agents to build experiences that look, feel, and work like Ramp—without a designer driving every decision or the design systems team reviewing every change. You’re a designer first, with the technical depth to guide architecture and get into the code. You have exceptional taste and strong opinions about typography, hierarchy, interaction, and motion. Just as importantly, you know how to turn that judgment into patterns, tools, and guidance that make everyone else’s work better. You’re deeply curious about AI and already using it to change how you work. You build, experiment, inspect the results, and push past the demo. You can imagine a different way of building software—and lead a team toward it. This role is for you if you’re excited by: - Making great design reproducible. Raise the quality of Ramp’s product and encode what makes it good, so people and agents can produce coherent, usable experiences by default. The system should make excellent work easier, not make every experience look the same. - Reimagining what a design system can be. Build beyond components and tokens into composition, interaction patterns, agent guidance, and evaluations. Connect exploration and production so the fastest way to build is also a path to great quality. - Leading a team that multiplies everyone else’s impact. Create clear direction, ambitious goals, and a caring yet demanding environment. Inspire curiosity, develop people, and stay close enough to the work to help make it exceptional. The opportunity is to raise the floor for everyone building at Ramp, while giving designers more room to make the most important experiences extraordinary. What You'll Do - Lead and develop the design systems team. Set clear priorities, ownership, and goals. Give direct, timely feedback, hold people accountable, and help them do the best work of their careers. - Own the system’s vision and direction. Decide what to preserve, evolve, simplify, or replace based on what builders and customers need. Turn that direction into focused work the team can deliver. - Elevate Ramp’s visual and interaction design. Raise the bar for typography, hierarchy, density, motion, responsive behavior, accessibility, and the states beyond the happy path. - Make design judgment usable by people and agents. Translate principles into reusable patterns, reference experiences, composition rules, and guidance that produce better work without you in the room. - Guide technical architecture with engineering. Shape everything from components and tokens to how agents discover guidance, compose interfaces, and check their work. Make sound tradeoffs between flexibility, coherence, performance, and ease of use. - Stay hands-on. Build prototypes, work in code, and get into implementation details to test ideas, unblock the team, and understand where the system breaks down. - Define and measure quality. Build repeatable evaluations grounded in real tasks. Measure whether builders can ship better work faster, with less rework—not just whether they use the tools. - Improve the path from idea to shipped experience. Partner with engineering and AI teams on workflows that support fast exploration, useful iteration, and appropriate production safeguards. - Earn adoption. Work alongside product teams, listen closely, teach through examples, and turn recurring questions and exceptions into improvements to the system. - Keep the team moving forward. Experiment as models and tools evolve, share what you learn, and change direction when the evidence calls for it. What You Need - Experience leading and

null

Lead and develop the design systems team. Set clear priorities, ownership, and goals. Give direct, timely feedback, hold people accountable, and help them do the best work of their careers. Own the system’s vision and direction. Decide what to preserve, evolve, simplify, or replace based on what builders and customers need. Turn that direction into focused work the team can deliver. Elevate Ramp’s visual and interaction design. Raise the bar for typography, hierarchy, density, motion, responsive behavior, accessibility, and the states beyond the happy path. Make design judgment usable by people and agents. Translate principles into reusable patterns, reference experiences, composition rules, and guidance that produce better work without you in the room. Guide technical architecture with engineering. Shape everything from components and tokens to how agents discover guidance, compose interfaces, and check their work. Make sound tradeoffs between flexibility, coherence, performance, and ease of use. Stay hands-on. Build prototypes, work in code, and get into implementation details to test ideas, unblock the team, and understand where the system breaks down. Define and measure quality. Build repeatable evaluations grounded in real tasks. Measure whether builders can ship better work faster, with less rework—not just whether they use the tools. Improve the path from idea to shipped experience. Partner with engineering and AI teams on workflows that support fast exploration, useful iteration, and appropriate production safeguards. Earn adoption. Work alongside product teams, listen closely, teach through examples, and turn recurring questions and exceptions into improvements to the system. Keep the team moving forward. Experiment as models and tools evolve, share what you learn, and change direction when the evidence calls for it.