[Hiring] Frontend Engineer @Restate

Role Description

We're looking for a Frontend Engineer to own the product experience across Restate's UI. 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. That makes it a different job from most frontend work.

You won't be doing this alone. You'll work closely with our design engineers, the wider product team, and the 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.
• State-of-the-art tech, built from first principles.
• 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.
• You’ll partner directly with engineers who’ve built and operated foundational systems at scale.

What you’ll do

• Own the frontend end-to-end: Architect, build and ship the product UI, from whiteboarding with engineers through to the production code you'll go on maintaining.
• Show what the system is actually doing: Execution timelines, retries, queues, state, failures.
• Build for data at scale: Large result sets, live updates, filtering and search that hold up.
• Make it fast: Restate is a low latency runtime and the UI should feel like one.
• Keep it safe to operate: Untrusted content, auth, and destructive actions all need more care than they would on an average frontend.
• Push the interaction model further: Keyboard navigation, deep links, state that survives a refresh.
• Grow the shared component library, so the product stays coherent as it gets bigger.
• Work closely with design and engineering: Skip the traditional handoff, iterate together, from first sketch to shipped.

Qualifications

• Strong opinions and shipped work that backs them up.

Requirements

• React and TypeScript: Several years of it, on an application big enough to get messy.
• Performance: You've profiled and fixed slow rendering, long lists, wasted re-renders, bundle size.
• Data-intensive interfaces: Datasets bigger than the viewport, pagination, virtualization, filtering, search, and charts built on real data.
• Data fetching and client state: Caching, invalidation, polling and streaming, optimistic updates.
• Security: Rendering untrusted content safely, auth and sessions.
• Information design: What to show, what to put one click away, what to leave out.
• Accessibility: Semantics, focus management, keyboard navigation, assistive technology.
• Reading beyond the frontend: API specs, queries, backend code.
• Testing: Unit and end-to-end, plus the judgement to know which tests are worth keeping.
• AI literacy: You use it daily to go faster.

Nice to haves

• Prior work on developer tools, observability, or infrastructure products.
• Data visualization: timelines, traces, graphs, time series.
• Building or maintaining a design system in production.
• Multi-tenant SaaS: environments, roles, quotas, usage.
• Willingness to open a PR on the back end when a feature needs an endpoint that isn't there yet.

Not a fit

• You expect a finished design to hand off, or heavy direction.
• You'd rather stay above the API layer.
• You want to run an engineering team rather than be the senior IC doing the work yourself.
• You're not interested in the technical subject matter.

Engagement, location, and travel

• Location: remote in Europe preferred; US remote for exceptional candidates.
• Travel: minimal; occasional team offsites.