Vice President, Product Design

Vice President, Product Designer – Job Description

The way products are built has changed. If you know how an .md file becomes experience design, this role may be for you. This role is based in New York, NY.

Design, product, and engineering don’t hand off to each other. They co‑create. We work from a shared repo that serves as a single source of truth: outcomes, strategy, personas, prototypes, and even presentations when we need them. Everything lives in one place and informs everything else in real time.

A designer on this team might start the morning synthesizing user research, open a repo, and have a testable concept in front of stakeholders by the afternoon. That’s not aspirational. That’s how the work moves.

How products are created is shifting under our feet, and we are embracing the opportunity and changing quickly. We believe the shifts with AI are enabling us to spend more time on crafting deeply user‑centric experiences with deliberate outcomes. When generation handles execution, designers focus on the problem, the user, and the quality of the experience.

• Make complexity clear. Take systems that are genuinely hard: multi‑step workflows, cross‑platform journeys, enterprise‑scale data. Design experiences that make sense to the people who depend on them. Understand the problem at depth before touching anything.
• Drive concept development from day one. Bring ideas from research and outcomes to prototyped form fast. Demonstrate possibilities rather than describing them. Use AI‑assisted tools to close the distance between design intent and working experience.
• Own the design of end‑to‑end experiences. Map journeys across users, teams, and systems. Identify where things break, where friction accumulates, and what needs to be rebuilt versus refined. Operate across the full scope of a platform experience, not just the screens in front of you.
• Contribute to a design system built for how design works now. Our design system is structured as machine‑readable infrastructure, not just a component library. Tokens carry semantic meaning. Patterns encode reasoning about when and why they apply. AI agents consume it directly alongside human developers. Contributing here means adding to the grammar, not just the vocabulary, and understanding why that distinction matters.
• Communicate design as a point of view, not a deliverable. Articulate the rationale behind decisions. Help product managers and engineers understand the tradeoffs. Make design legible to people who don’t speak design, without dumbing it down.
• Mentor through example. Raise the standard of work around you through critique, collaboration, and how you approach problems. Not through title.

• Strong product design fundamentals: research synthesis, interaction design, systems thinking, visual craft.
• Experience designing complex systems: enterprise software, multi‑step workflows, data‑heavy interfaces.
• Demonstrated comfort working in ambiguous, fast‑moving environments where the problem isn’t handed to you pre‑formed.
• The ability to communicate design rationale to mixed audiences (product, engineering, business) and hold your perspective under pressure.

• Experience with AI‑assisted tools, not just for ideation but for building and prototyping.
• Experience working in shared codebases or repos with cross‑functional teams, or actively moving in that direction.
• A description of a moment when AI changed how you approached a design problem, not just made it faster but made it different.
• Contribution to a design system at the pattern or systems level, not just component execution.

• Work at the intersection of design and technical implementation, close to the material,…