Product Designer

Product Design's charter at Arcade is simple and hard: every surface where customers meet Arcade is a trust surface. For most of our customers - the AI/ML architects deploying Arcade inside their companies - the Dashboard is the only place they see us today, which is why it's where you start. Every fear they have about giving agents access to real systems either gets settled or amplified here.

The work of design is to make sure it's the former.

This is a new design space. Agents are non-deterministic. Tools fire in patterns customers didn't predict.

Auth scopes nest in ways that aren't obvious. The Dashboard has to make all of that legible - for an admin granting an agent permission, an engineer debugging a failed tool call at 11pm, a compliance reviewer asking "what did the agent actually do?" Three different mental models, one product surface.

There is no playbook for this. Nobody has shipped a definitive answer for how to design an admin UI for agents - the conventions we adopt will likely become the ones other companies copy. Some of your work is design.

Some is teaching, explaining concepts customers haven't fully internalized yet, inside the product itself. If you'd rather inherit a design language than help invent one, this isn't the right role.

And you're not just designing - you're building a function. There's no design team yet. There's no design language you inherit (engineering has stood up Radix and Tailwind patterns, but those are a starting point, not a system).

You'll define how design works with engineering, how it works with the PM, and how it shows up in Marketing. Every pattern you set becomes the one the next designer inherits.

This role reports to the Engineering Manager for Tools and Growth. The team is small, and you'll work across the entire company - shoulder-to-shoulder with engineering on the Dashboard, with the PM on Tools and Growth on what surfaces matter most, and with Marketing on how design decisions show up beyond the product. Your decisions land in customers' hands within weeks, not quarters.

If you want to do the design work nobody has done yet - and watch customers learn from it - this is the role.

- Own the design of major Dashboard surfaces end-to-end - flow, interaction, visual - from first sketch to shipped pixels.

- Run customer research with the AI/ML architects deploying Arcade. Interview them. Watch them use prototypes.

Bring the signal back to the team.

- Pair daily with engineering. Hand off in Figma, watch implementation in our React + Tailwind codebase, and iterate when production reveals something the mock didn't.

- Shape the design system alongside engineering. We use Radix and Tailwind today; what we ship next either reuses, extends, or replaces those patterns deliberately.

- Make agent state legible - tool execution, auth scopes, observability, billing. All of it has to feel obvious in the moment a customer needs the answer.

- Write the design rationale. Explain decisions so engineers, the PM, and Marketing can build on them - and so customers learn the model from the product itself.

- Set the bar for design quality as Arcade grows. Your patterns get inherited by every designer after you.

- 3-5 years of product design experience, with at least one role focused on a developer-facing or B2B SaaS product. Formal title matters less than the work.

- A portfolio that shows end-to-end product work - research → flows → interaction → visual → shipped pixels, not just static screens.

- Strong fluency in Figma. Fast, organized, components and tokens you'd actually want to inherit.

- Comfort with technical product spaces. You can read enough about APIs, auth, and agent behavior to design for them - and you ask the right questions when you can't.

- Demonstrated ability to run customer research without a dedicated researcher. You've talked to real users, synthesized what you heard, and changed the design because of it.

- Strong partnership with engineering. You've shipped real product alongside engineers and made the work better for it.

- Opinions on design systems - not just visual consistency, but how tokens, components, and patterns hold up as a team scales.

- Comfort with ambiguity - early team, narrow charter that will expand. You make good decisions with incomplete data.

- You've designed for AI, ML, or agent products before - and have opinions about what makes them work.

- Prior experience at a developer-tools, API-platform, or infrastructure company (Stripe, Vercel, Supabase, Auth0, Postman, Linear, and the like).

- You've shipped or substantially contributed to a design system that survived contact with multiple engineers.

- Comfort designing for engineers as your primary user - you understand what makes an admin UI feel right to someone who'd rather be in their terminal.

- Prototyping in code, even at a basic level. A designer who can read React and prototype interactions in the actual codebase moves faster than one who can't.

We're not just building a product; we're leading a movement to transform AI from just chatbots to agents that can take actions against real systems. This is your chance to be at the forefront of that revolution.

- This is an in-person role located in our San Francisco (SOMA) office.