Product designer, Traces
Make a forty-step run readable in a minute, for the people who didn't build the agent.
A trace is the record of a run: what the agent read, what it decided, who approved what. It's how a support lead answers "why did this customer get a refund?" and how an engineer finds the step that went wrong. Last year we rebuilt it so anyone on a team could read a run top to bottom in a minute. Now teams run agents with forty steps and six tools, and we need to do it again.
You'll join Jonas Weber and Elif Kaya, and work closely with the Runs and Replays engineers.
What you'll do
- Own the trace view, from a single step to a run with approvals, retries and a budget stop.
- Design how people compare runs: this week against last, the agent against a person, before and after a change to its instructions.
- Turn what we learn from customers into small, shipped changes every week, not a redesign every year.
- Write the words. In a trace, the sentence that says what happened is the design.
- Test your work with real teams and real runs, and bring the recordings back to us.
What you'll bring
- A portfolio of shipped product work on dense, data-heavy tools, with the reasoning behind it.
- You prototype in code or in a tool close to it, and you care what happens at 390 pixels wide.
- Strong typographic judgement. Most of a trace is text.
- You ask to sit with users, and you're good at it.
Nice to have
- You've designed logs, observability tools, developer tools or a support product.
- You've worked in a design system and made it better.
Where you'll work
In our Stockholm office, or with the team in Berlin three days a week. We'll help with relocation to either.
Sample role. Replace the files in content/careers with your own.