What it's like to join WorkOS as a product designer

Most product design roles follow a familiar pattern: frame the problem, design it in Figma, hand off a spec, and wait to see what ships. WorkOS works differently. "AI-native" gets said a lot right now, and I'll admit it sounded like a buzzword to me too. It's one of those things you only really understand once you're inside a company that lives it.

Designing at WorkOS means the whole picture is already at your fingertips: the data, the customer conversations, the decisions behind them. Here's what that actually looks like day to day.

Data and context within reach

In previous jobs, getting data was always a small ordeal. It lived somewhere I couldn't reach, or it arrived in a form I couldn't confidently interpret. At WorkOS, "how many customers use this feature?" or "what feedback have we gotten on this feature?" are questions I answer myself in a couple of minutes. Our data platform is wired up through MCP. I can ask in plain language and get a real number back, instead of waiting for access or waiting on someone to reply.

What makes it trustworthy, not just fast, is that it feels like asking our data team directly. They built a skill that bakes in the same perspective they use: the company's shared definitions. It encodes what actually counts as a customer, as "paying," and as product adoption, and it sends every question to the modeled data, not some raw table I might have guessed at. So the number I get is the same number everyone else gets, not my personal interpretation.

Transparency

We have shared Slack channels with the people who use our products, and those conversations aren't locked in a sales CRM I'll never see.

This transparency extends to how the whole company runs. WorkOS is radically transparent by default: meetings get recorded, questions get asked in public, decisions get written down where anyone can search them. Nobody hoards context.

Combine that with connectors into Notion and Slack, where our internal decisions and our actual conversations with customers live, and it becomes easy to connect the dots: the metric, the reasoning behind a past decision, and the customer who asked for it, all in one place.

These tools meaningfully sped up my onboarding. Instead of the traditional months spent slowly accumulating enough context to be useful, I could pull that context on demand and start contributing meaningfully much more quickly.

AI isn't a side experiment

Experimenting is encouraged, loudly. There are more than enough AI credits, a stack of tools to try, and company-wide events built around building. Every month there's a dedicated "Claude Day," an internal one-day hackathon where we're encouraged to build AI workflows that make our own jobs better. This produces truly meaningful results, not just gimmicks or fun experiments.

For designers specifically, Figma is just one surface. A lot of experimentation happens in the browser: designing directly in code and iterating on the live product instead of a static mockup. Designers alone have used Claude Days to build tools such as a shared canvas for commenting on work-in-progress, an auto-organizing inspiration board, and a bot that triages and catches UI bugs on its own.

Designing at WorkOS

If you've spent years designing inside constrained environments, working around missing context and locked-down data, WorkOS will feel like those constraints just lifted.

We're growing the team. If this sounds like how you already want to work, come build with us.