Design Engineer
Posted 17 Sep 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Management level
- Individual contributor
- Employment
- Remote
- Contract
- Full-time
No salary listed for this role.
The Opportunity
We're looking for a Design Engineer to own the core Restate UI, design and code.
Our UI is where developers end up when something is running, stuck, or has already gone wrong. It's a live window onto a distributed system that keeps moving while you're looking at it. The data is large, it changes under you, and the person reading it is usually in a hurry.
Developers already like Restate for making something technically complex feel simple. Holding that as the product grows is the job, and you'd hold it end to end: the design decisions and the code that ships them.
Why Restate
Durable runtimes are becoming the next foundational infrastructure layer, especially for AI. Restate’s vision is to make durable execution efficient and lightweight to run.
Restate is built by a team of world-class engineers - the creators of Apache Flink, leaders from Meta's messaging infrastructure, and senior engineers from AWS and Confluent.
AI-native companies like Replit as well as Fortune 500 enterprises rely on Restate in production for their core applications.
With a fresh $20M Series A fundraise by top tier investors and strong traction, we’re just getting started and are looking for people who share our vision and work ethos.
What you’ll do
We want to hire a great Design Engineer to ensure a stellar developer experience across the core Restate UI and adjacent parts of the product. The scope includes but is not limited to:
-
Architect, design and ship the core Restate UI: from whiteboarding sessions with engineers to production-ready code.
-
Show what the system is actually doing: execution timelines, retries, queues, state, failures. People come to the UI to work out what happened, often while something is on fire, and it has to get them there quickly.
-
Build for data at scale: large result sets, live updates, filtering and search that hold up, and the charts and timelines that sit on top of them.
-
Design the states nobody designs: loading, empty, partial, error, one result and far too many. A developer tool is won or lost in those, and they're usually the ones that get skipped.
-
Keep it fast: Restate is a low latency runtime and the UI should feel like one. Rendering cost, data loading and perceived latency are design decisions here, not a cleanup pass at the end.
-
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.