Note: The job is a remote job and is open to candidates in USA. Replicant is an AI company focused on customer service, providing AI agents and conversation intelligence for contact centers. The Director, Product Design will lead Replicant’s design practice while remaining approximately 80% hands-on, owning the customer experience, information architecture, design system, prototype-and-validation process, and integration of product and conversation design.
Responsibilities
- Own the whole customer experience, interface included. A customer's experience of Replicant runs from the sales conversation, through a deployment our delivery team configures, into an AI agent that talks to •their• customers, and back out through the analytics their operators read daily
- Set the information architecture for a converging platform. Our conversation intelligence and agent-building products grew separately and are now becoming one product. You decide what the objects are, what they're called, and how someone moves between them
- Own the design system's architecture and the rules around it. The foundation exists — components in Figma and in Storybook. What's missing is a pattern language, documented decisions about when to use what, and a contribution model engineers can build against. You set that architecture, govern it, and are accountable for it existing
- Extend design's influence past the work you do yourself. Much of the customer-facing experience here gets shaped by people outside your team: product managers, delivery engineers who configure agents, solutions engineers in demos. Raising the bar means influencing them, giving them something good enough to follow, and telling them no when it matters
- Drive rapid prototype-and-validation loops. You'll talk to internal customers, contact center operators and turn what you hear into design decisions, owning method as well as findings. You’ll create and drive a best-in-class prototype-and-validate loop
- Bring product design and conversation design together. Our product •is• a conversation, so we've put both disciplines in one practice. You own how they come together and the research practice underneath both
Skills
- • You think in systems and journeys. Before asking which control a step needs, you ask whether the step needs to exist. You've designed across touchpoints that weren't all interfaces: a call, a handoff, an email, a conversation with a human agent
- • You have a real HCI or interaction-design foundation. You can reason from first principles about how people perceive, learn, form expectations, and recover from error, rather than from patterns you've seen in other products. Voice, conversational, and graphical interfaces all sit inside our product, and we need someone who can move between them without starting over each time
- • You've driven change through resistance. You've moved an entrenched team over months, not just changed one executive's mind in one meeting. You can describe what you were up against and what it took
- • You think in business terms without being asked. You've spent time close to the PM role, or worked with product closely enough that you think that way anyway. You can point to specific decisions that changed because of a conversation you personally had with a customer
- • You've governed a design system, not only built one. Contribution, documentation, deprecation, and the arguments that come with them. You can describe a time you told someone no and why. The governance matters more to us than how many components you drew
- • You find the problems and set your own priorities. You identify opportunities the team hadn't seen and make the case for them. You converge without being pushed and escalate the right things at the right time
- • You're AI-native in your practice. You use these tools in real design work and have earned opinions about where they help and where they degrade quality. You've built workflows or assets other people adopted
- • You lead people and hold a room. Setting direction, giving hard feedback, running a critique, growing someone's craft, and hiring. You can also hold your position in front of executives and customers. Formal management experience helps; evidence that designers got better working with you matters more than a title
- • Based in a US or Canadian timezone
- • 10+ years of product design experience
- • Experience leading or growing designers, whether or not you had the title
- • Experience owning design for an enterprise or operational product
- • Figma fluency on the system side: components, variants, libraries, variables, tokens. Enough to hold your hire to a standard and to work in the files yourself
- • Comfort moving between Figma and code (Storybook, shadcn/ui, Tailwind, or tools like Cursor and Claude Code). If you want to pick up UI-level changes yourself, that's open to you with preview environments and engineering review
- • Experience designing AI or conversational products, especially where the output was non-deterministic and you had to design failure states, trust, correction, and recovery
- • Experience with operational or contact center tooling
- • Experience defining a design practice from close to nothing
- • Experience leading designers across more than one discipline — product, conversation, content, or research
Benefits
- Company-wide offsites and smaller team gatherings designed to make remote work feel personal
- Tech & learning stipend for conferences, books, and courses
- Remote work arrangement with calendar flexibility for life events
- Flexible vacations
- Paid sabbatical after 5 years
- Comprehensive benefits
- Stipend to support physical and mental well-being
- Equity with shared ownership in the company
Company Overview