Founding Designer at Sable (San Francisco, CA)Founding Designer

Sable built Aidan, the first AI employee who can lead customer calls using realtime voice, vision, and browser use. Aidan runs a live, two-way conversation inside a real product environment, clicking through the product like a human, watching the user's screen, and adapting the journey on the fly. Every conversation feeds a self-improving context graph we call the Brain, so Aidan gets smarter with each call.

You are Sable's first designer. You define what design is here. Sable's product surface area is unusually large for one person: the platform where customers build and manage AI employees, the live call interface where Aidan meets end users, the brand, the marketing that carries it — and the system that keeps all of it coherent as we scale. Much of this has no precedent. Nobody has worked out what it should feel like to build an AI employee who runs your customer calls, or how an AI employee earns a stranger's trust in the first seconds of a conversation. You'll get strong opinions from the team and customers here. Treat them as raw material: extract the real insight, then make the call with taste and a reason behind it.

• Own product frontend design: from ambiguous problem to visual experience, across the customers who deploy Aidan and the people who talk to him
• Define Sable's brand: visual identity, marketing site, and how an "AI employee" presents itself to the world; you set the voice and the look for a category we're creating
• Prototype in code and work shoulder-to-shoulder with engineers, catching design drift, actioning it, and integrating it without slowing down deployment
• Drive your designs through implementation to live: run tight iteration cycles with engineering, see what holds up with real users, and ship the next version
• Design with the founders: bring options, articulate tradeoffs, and incorporate feedback without losing the thread

• 2–5 years of product design experience, with shipped work you're proud of
• Strong UX thinker: you reason from user problems, not aesthetics-first, and your interfaces hold up under product pressure
• You've built or meaningfully shaped the design of a full system
• Comfortable close to code: you can prototype and have worked tightly enough with engineers that implementation is an ongoing conversation, not a handoff
• Resilient and decisive: you take pointed feedback from opinionated people, separate signal from noise, and defend your decisions with reasoning, not vibes. You are willing to change your mind when the facts change

Explicitly not this role: a Figma-only designer who hands off specs; a pure brand/marketing designer with no product depth; a design leader who needs a team to manage before doing the work