The design system. Architecture, components, and motion. You should be familiar with design.md files and enforcing usage in an AI-driven environment
Interaction design for major surfaces, from how something should behave through the shipped UI
Establishing the product’s visual direction and evolving it as the product surfaces expand
Pushing PRs of frontend polish in the codebase (don’t worry, we’re very AI-friendly)
Contribute to solving product problems with the lead designer and PM, then taking the craft the rest of the way
WHAT YOU'D BE DESIGNING
Customers use our dashboard to build, test, evaluate, and run LLM voice agents. Behavior gets configured instead of scripted, none of the outputs are deterministic. Our users are technical and non-technical, from CIOs and call center experts to our in-house FDE team
We're most of the way through a ground-up redesign of the dashboard and we’ll be landing it in the next quarter, so this role will be a major contributor early and meaningfully
Opening a PR in the morning and merging it that afternoon is completely normal, and it's one of the better things about working here
Priorities move around. You might start the week on one surface and spend Wednesday somewhere else, and you'll usually have three or more things going at once
That pace depends on AI tools. Running several Claude sessions at once to keep your PRs moving is an ordinary day around here, and we expect you to keep pushing on how you work
The bar is high and we're not shy about it. We want the design held to the same standard as the model: good enough that other people in voice AI look at what we ship and copy it
Brand-level thinking—Product has the opportunity to both work with and make changes to our brand
Motion or generative visual work
Ability to write coherent FE code