Redpanda is the first runtime and control plane for agent-data interaction — a unified platform that combines streaming, SQL analytics, and intelligent connectivity with the governance layer enterprise AI agents need in production.
Built on infrastructure already trusted by Fortune 500 companies and fast-growing startups, Redpanda enforces governance entirely outside the agent's data path, controlling what agents see, limiting what they do, and capturing a tamper-proof record of everything they touch, so organizations never have to choose between innovation and control.
About the Role:
We're looking for an experienced Staff Software Engineer to own the UI platform every Redpanda product is built on, and to lead its migration to product-based microfrontends.
Redpanda Cloud is the front door to everything a customer touches: Redpanda Streaming, Connect, SQL and the Agentic Data Plane. It already composes several of those surfaces at runtime through Module Federation, and that will grow as products move to their own teams and their own release cadences behind one experience. You'll own the architecture of that shared layer - the host shell and remote contracts, the build and release pipeline, the testing and observability story, and the frontend standards that stop every team solving the same problem a different way.
We already have strong contributors across our product surfaces and design system, and you'll be setting the structure they build inside.
The migration is the biggest piece of work, but it isn't the whole job. You'll decide how Redpanda's UI is composed for the next several years - what a product surface owns, what the platform owns, and what the contract between them looks like. That shapes how every frontend engineer here works.
This is a hands-on individual contributor role. You'll lead through architecture and the standards you set, not through direct reports.
You'll be based in our growing Warsaw office, alongside the team that owns our commerce path including sign-up, usage-based billing, payments and cloud-marketplace integrations, and you'll set direction on the shared customer-facing surfaces for frontend engineers across both EMEA and the Americas.
Our engineers increasingly build frontend surfaces with AI coding agents doing a large share of the implementation. We need our design system to be able to scale under that model. You'll treat "can an agent consume this design system correctly, unsupervised, and produce something on-brand and accessible" as a real design constraint, alongside "can a new hire."
You Will
- Own the Redpanda UI platform end to end: host shell, remote module contracts, versioning and compatibility, shared dependencies, routing, auth, and the runtime failure behaviour of the whole composition
- Set the architecture and migration path for splitting product surfaces into independently deployable microfrontends, and drive alignment and delivery with the teams who own those products across EMEA and US time zones
- Define the graceful degradation and fallback patterns that keep Cloud usable when a remote is missing, stale or incompatible
- Raise release confidence with uniform end-to-end and certification tests across environments
- Set and uphold frontend standards through RFCs, design review and code review, and make them easy to adopt
- Contribute to and evolve the design system and component library, keeping components composable across independently deployed surfaces
- Represent frontend in cross-team architecture discussions, so API and information architecture decisions land well in the UI
- Participate in the on-call escalation chain, helping reduce escalations and improve operational health
- Raise the engineering bar and mentor engineers across the UX and product teams
You Have
- Significant experience building and operating production-grade customer-facing web applications at scale with React and TypeScript, including ownership of a shared platform, framework or design system that other engineers depend on
- Production experience with microfrontend architecture and Module Federation, or an equivalent such as single-spa or native federation, including version skew between host and remotes, shared dependency management, runtime failure modes and independent deployment
- A track record of leading large technical projects end-to-end, from design and planning, to execution and production operations
- A track record of setting architectural guidelines and driving adoption across multiple teams
- Depth in modern frontend fundamentals: component architecture, state management, data fetching, build and runtime performance, and accessibility
- Experience with AI-assisted software development workflows including tools like Claude Code
- Fluency with frontend testing, unit through end-to-end, and clear opinions on what belongs in CI, what belongs in pre-production and what belongs in production monitoring
- A strong design sensibility. You care how the product looks, feels and behaves, and you can hold a quality bar without a designer in the room
- Excellent written and verbal communication skills in English; comfortable working in a globally distributed, async environment (e.g., GitHub)
- Ability to collaborate effectively with engineering, product, design and customer-facing stakeholders
Nice to Have:
- Experience adopting, modernising, and rearchitecting frontend systems
- You think deeply about how both humans and LLMs can work together to produce consistency and uphold quality in both design and code
- Depth in one or more of: monorepo tooling at scale (Nx, Turborepo, pnpm workspaces), bundler and federation internals (Vite, Rspack, Webpack), design-system-to-code pipelines (Figma tokens, codegen, visual regression)Enough Go familiarity to read and change the services this UI talks to, and to hold your own on API design with the teams that own them. You don't need to be a G
Sourced directly from the company's job board — apply on their site.