Product Designer

Product Designer at Restate

Restate (restate.dev) is a lightweight runtime that turns AI agents, workflows, and backend services into durable processes - so teams can focus on their logic, not failure mechanics.

The role: We're looking for a Product Designer to shape Restate's core product experience.

This role covers both, the core Restate UI with the design system behind it and the visual work that makes durable execution understandable to developers.

You'll work directly with the engineers who build the product and with the wider founding team.

The opportunity

Front-row seat to the biggest infra shift in decades

Durable runtimes like Restate are becoming the next foundational infrastructure component - and increasingly a critical piece for AI applications. As systems become more agentic, long-running, integration-heavy, and failure-prone, durable execution turns reliability from a bespoke engineering tax into a default property. In this role, you’re not watching that shift from the sidelines - you help build the platform that enables it.

State-of-the-art tech, built from first principles

Restate re-imagines durable execution as a lightweight self-contained stack - no database required - and ships as a single Rust binary with an optimized custom storage layer, low latency orchestration, and an analytics engine for observability.

Enterprise Traction

Restate is already used by Fortune 500 companies, including Tier 1 banks running critical financial workflows, and also by cutting-edge AI and infra startups pushing the boundary of what “production-grade agents” mean. You’ll work on problems where reliability, correctness, and operational simplicity are existential.

Work with world-class engineers

You’ll partner directly with engineers who’ve built and operated foundational systems at scale - creators of Apache Flink, and leaders from Meta’s messaging infrastructure. You’ll have the chance to work with incredibly talented individuals who care deeply about their craft.

What you’ll do

On the core product:

• Design the core Restate UI: from whiteboarding sessions with engineers to shipping. You won't be writing the production code, but you stay with it until it's right.

• Make dense information readable: execution timelines, retries, queues, state, failures. Our users are engineers working out what happened, usually in a hurry, and deciding what they see first is most of the work.

• Keep one mental model: developers meet the same concepts in the UI, the SDKs and the docs. They should be named and presented the same way wherever someone runs into them.

• Bring durable execution to life visually: the current Restate product is loved for its simplicity in breaking down a technically complex product. You'll make sure we keep shipping at the same design bar.

Around the product:

• Explain Restate's architecture visually: interactive and animated explanations that make the key differentiators clear.

• Motion as a first-class medium: Restate is a living, durable system, and we want to design with motion to convey that.

• Ship across surfaces: developer-facing content, blog illustrations, social visuals, and more.

• Keep it coherent with the product: the visual language that explains Restate from the outside and the one inside the product should be the same language.

Across both:

• Build scalable design systems: reusable components and patterns for architecture diagrams, code visualizations, and interactive elements that others can benefit from.

• Work closely with design and engineering: skip the traditional handoff and iterate together, from first sketch through to shipped.

What we’re looking for

The profile

We're looking for a product designer with strong opinions and a portfolio that backs them up, covering both halves: complex product work you've designed, and visual work that explains something technical. You should be comfortable operating with significant autonomy, working directly with the founding team, and pushing back when the team is wrong.

You don't have to write production code. You do have to understand what you're designing for well enough to have the argument with an engineer and sometimes win it.

Must-haves:

• Product design depth on complex software. Several years designing tools, dashboards, or platforms. Not only marketing sites and consumer apps.

• Information design. Turning a lot of data into something a person can read quickly. Hierarchy, density, progressive disclosure, and knowing what to leave out.

• Visual storytelling for technical concepts. Show us how you've made something complex feel obvious.

• Brand and campaign craft. Layout, typography, illustration, launch visuals. Work that stands up next to the best in developer tools.

• Motion design ability. Motion as a way to communicate state, time, and dynamism.

• Design systems. Reusable components and patterns others can build on, and the discipline to keep them coherent over time.

• Strong design sensibility. A high visual bar you can hold across the product and the work that explains it, without waiting for someone to set the direction first. We're not precious about which tools you get there with.

• Technical curiosity. You don't need a distributed systems background, but you should be able to follow what the product does and design from understanding rather than from a screenshot.

• Writing. Labels, empty states, error messages, headlines.

• AI literacy. You're using AI to multiply your own impact and to unblock yourself.

Nice-to-haves:

• Prior work on a developer tools, infrastructure, or AI product. Familiarity with the developer audience and what "great" looks like in this space.

• Experience building or contributing to a design system in production.

• Prototyping in code, or enough HTML and CSS to communicate an idea precisely.

Not a fit:

• You've only designed complex software, or only made things look good from the outside. We need both.

• You expect a finished brief, or heavy direction. We need someone who arrives with a point of view and designs.

• You want to lead a design team rather than be the senior IC doing the work yourself.

• You're not interested in technical subject matter. Our surface area is wide, and the role lives or dies on translating it.

Engagement, location, and travel

• Location: remote in Europe preferred; US remote for exceptional candidates

• Travel: minimal; occasional team offsites.