About the role
About us: At Reevo, we're reimagining the entire revenue stack from the ground up, and we're doing it with speed. We're building software that orchestrates every go-to-market motion, enabling B2B teams to operate faster, smarter, and more collaboratively. By combining automation, intelligence, and a radically intuitive interface, we're helping companies unlock new levels of productivity and growth across marketing, sales, ops, and customer success teams. If you're excited about working on a product that reshapes how revenue teams work and being surrounded by curious, driven teammates, you'll feel right at home here. From day one, you'll get real ownership, real mentorship, and real impact. Our team of 100+ builders has over 30 exits under their belt, so you'll be in good company, and working alongside the best!
The Role: We're looking for an experienced product designer to own our design system. This is the person who makes it possible for every team at Reevo to build consistent, high-quality experiences quickly, and who understands that the components are only part of the job. The documentation, the socialization, and the governance are what determine whether a system actually gets used. Our design system is early, and the foundational decisions are still ahead of us. You'll drive how we make them, with design and engineering shaping them alongside you. Your customers are the designers and engineers who build on the system. It's also the foundation our AI agents build on, which makes it a product surface in its own right, not just internal scaffolding. The best systems designers have sat on the other side of the table: they've shipped product work themselves, they still take some on, and they design the system around what that work actually demands. What You Will Do: Own the Design System: Own the system end to end, from components and documentation to governance and the roadmap. You'll drive what gets built next and pull in design leadership where you need support. Build for Scale: Build and evolve a system that goes from tokens through atomic components to composed patterns, holds up across platforms, and is structured so our AI agents can generate on-system experiences, working alongside the engineers who implement it. Iterate Rapidly: Prototype and pressure-test components and patterns, iterating on them with the designers and engineers using them and against user feedback and business goals. Make Documentation Self-Sustaining: Own how the system is documented by designing the tooling and process that keep guidance current and useful, so designers, engineers, and our AI agents know not just what a component is, but when and why to use it. Stay in the Product: Take on end-to-end product design work that stress-tests the system in real use. Serve Design and Engineering: Build deep relationships with the designers and engineers who depend on the system, understand what's blocking them, and prioritize the work that unblocks them. Socialize and Govern: Drive adoption across teams, review contributions, and hold the quality bar with guardrails that keep what ships on-system whether a person or an agent is building it, without becoming a bottleneck. What We’re Looking For: 8+ years designing products in a fast-paced environment, ideally in B2B SaaS, with 2+ of those years building and owning a design system A product design background that includes shipping end-to-end product work, not only systems work Demonstrated ownership of a system beyond its components: documentation, contribution and governance models, adoption, and versioning A track record of earning trust with designers and engineers, and of letting their needs drive your roadmap Fluency in how components get built, and comfort in the conversation with engineers about component APIs, tokens, and implementation tradeoffs Genuine interest in building a system that AI agents create with. You don't need to have done it before, but it's central to where ours is going A self-starter who is comfortable in ambiguity. You find the problems, decide what matters, and move, pulling in leadership when you need support rather than permission A high craft bar and the persistence to hold it, including in the parts people skip: edge cases, deprecations, and keeping docs current What we offer: