Staff Software Engineer, UI Platform

Redpanda Data
Full-time

📍 Job Overview

Job Title: Staff Software Engineer, UI Platform

Company: Redpanda Data

Location: Warsaw, Masovian Voivodeship, Poland

Job Type: FULL_TIME

Category: Frontend Engineering / UI Platform

Date Posted: 2026-09-15

Experience Level: 10+ years

Remote Status: Hybrid (with primary office in Warsaw)

🚀 Role Summary

  • Lead the architecture and migration of Redpanda's UI platform to a microfrontend-based system, enabling independent product team deployments.

  • Own the end-to-end lifecycle of the UI platform, including host shell, remote module contracts, versioning, shared dependencies, and runtime behavior.

  • Define and enforce frontend engineering standards, component architecture, and design system evolution to ensure consistency and scalability, particularly for AI-assisted development.

  • Drive adoption of architectural guidelines and best practices across multiple distributed frontend teams, fostering a culture of technical excellence and collaboration.

  • Contribute to operational health by participating in the on-call escalation chain and improving observability for the UI platform.

📝 Enhancement Note: While the job title is "Staff Software Engineer, UI Platform," the responsibilities strongly indicate a senior-level individual contributor role focused on frontend architecture and platform strategy, rather than a traditional "operations" role. The emphasis on platform ownership, microfrontend architecture, and setting standards aligns with a senior engineering leadership track within the frontend domain.

📈 Primary Responsibilities

  • Architect and oversee the end-to-end Redpanda UI platform, encompassing host shell, remote module contracts, versioning strategies, shared dependency management, routing, authentication, and runtime failure handling for the composed application.

  • Define and execute the architectural roadmap for migrating existing product surfaces into independently deployable microfrontends, ensuring alignment and timely delivery with product teams across EMEA and US time zones.

  • Establish robust graceful degradation and fallback patterns to maintain Cloud usability even when remote modules are unavailable, outdated, or incompatible.

  • Enhance release confidence through the implementation of uniform end-to-end testing strategies and certification processes across various environments.

  • Define, document, and advocate for frontend engineering standards via RFCs, design reviews, and code reviews, ensuring ease of adoption for all engineering teams.

  • Drive the evolution of the design system and component library, ensuring components remain composable and consistent across independently deployed frontend surfaces.

  • Represent frontend interests in cross-team architectural discussions, ensuring API and information architecture decisions are effectively integrated into the UI.

  • Actively participate in the on-call escalation process to reduce escalations and enhance the operational health and stability of the UI platform.

  • Elevate the overall engineering quality and mentor engineers across product, UX, and frontend teams, fostering continuous learning and skill development.

📝 Enhancement Note: The responsibilities are heavily focused on architectural leadership, platform strategy, and technical mentorship within the frontend domain, aligning with a Staff Engineer role. The emphasis on microfrontend migration, design system evolution, and operational aspects like testing and observability are key for candidates to highlight.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a strong foundation in Computer Science principles is implied through the experience requirements.

Experience: Minimum of 10 years of professional software engineering experience, with a significant focus on frontend development and platform ownership.

Required Skills:

  • Extensive experience building and operating production-grade, customer-facing web applications at scale using React and TypeScript.

  • Proven track record of owning a shared platform, framework, or design system that serves as a critical dependency for other engineering teams.

  • Hands-on production experience with microfrontend architecture patterns, including Module Federation, single-spa, or similar, with a deep understanding of version skew between hosts and remotes, shared dependency management, runtime failure modes, and independent deployment strategies.

  • Demonstrated ability to lead large, complex technical projects from conception and planning through execution and ongoing production operations.

  • A history of defining architectural guidelines and successfully driving adoption across multiple engineering teams.

  • Profound understanding of modern frontend fundamentals, including component architecture, state management, data fetching strategies, build and runtime performance optimization, and web accessibility standards (WCAG).

  • Experience with AI-assisted software development workflows and tools such as Claude Code, with an understanding of how to leverage these for efficiency and consistency.

  • Fluency in frontend testing methodologies, from unit tests to end-to-end tests, with clear opinions on their placement within CI, pre-production, and production monitoring stages.

  • A strong design sensibility and a keen eye for product aesthetics, feel, and behavior, with the ability to maintain a high-quality bar independently.

  • Excellent written and verbal communication skills in English, with proficiency in asynchronous collaboration tools like GitHub.

  • Proven ability to collaborate effectively with cross-functional stakeholders across engineering, product, and design teams. Preferred Skills:

  • Experience in adopting, modernizing, and rearchitecting existing frontend systems.

  • Deep thinking about how both humans and AI (LLMs) can collaborate to ensure consistency and uphold quality in both design and code implementation.

  • Expertise in one or more of the following:

    • Monorepo tooling at scale (Nx, Turborepo, pnpm workspaces).
    • Bundler and federation internals (Vite, Rspack, Webpack).
    • Design-system-to-code pipelines (e.g., Figma tokens, codegen, visual regression testing).
  • Familiarity with Go to the extent of reading and modifying services the UI interacts with, and contributing to API design discussions with Go-focused teams.

  • Experience with protobuf, ConnectRPC, gRPC-web, or advanced data-fetching libraries like react-query.

  • Experience implementing and managing feature flag platforms (e.g., LaunchDarkly) at scale.

  • Experience with frontend delivery platforms like Netlify and with synthetic monitoring practices.

  • User-level experience with streaming platforms such as Redpanda or Apache Kafka.

  • Prior experience working in an early-stage or growth-stage startup environment.

📝 Enhancement Note: The emphasis on "10+ years" for experience level suggests a need for deep, specialized knowledge and a proven ability to lead complex initiatives. The "Nice to Have" section provides excellent opportunities for candidates to differentiate themselves by showcasing niche expertise relevant to Redpanda's technology stack and vision.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

  • Showcase a history of architecting and delivering complex, scalable frontend applications, ideally involving platform-level responsibilities or shared component libraries.

  • Present detailed case studies of significant technical challenges overcome, demonstrating problem-solving skills and strategic thinking in areas such as microfrontend implementation, performance optimization, or cross-team standardization.

  • Provide examples of how you've influenced and improved engineering processes, such as testing strategies, CI/CD pipelines, or code review practices within a frontend context.

  • Illustrate contributions to design systems or component libraries, highlighting their impact on developer productivity, product consistency, and maintainability. Process Documentation:

  • Demonstrate experience in documenting architectural decisions, platform contracts, and migration strategies, particularly for microfrontend initiatives.

  • Highlight your approach to defining and implementing frontend standards, including RFC processes, design review mechanisms, and code quality enforcement.

  • Showcase examples of how you've established and monitored key performance indicators (KPIs) for frontend applications, focusing on metrics related to performance, reliability, accessibility, and developer experience.

📝 Enhancement Note: For a Staff Engineer role focused on a platform, the portfolio should emphasize architectural vision, leadership through technical influence, and the ability to drive cross-team alignment on complex technical initiatives. Demonstrating tangible outcomes from platform ownership is crucial.

💵 Compensation & Benefits

Salary Range: Given the Staff Software Engineer title, 10+ years of experience, and location in Warsaw, Poland, the estimated annual gross salary range for this role is likely between €75,000 - €110,000.

  • Methodology: This estimate is based on research for senior/staff-level frontend engineering roles in major European tech hubs, specifically Warsaw, which has a competitive but generally lower salary ceiling than Western European or North American equivalents. The range accounts for the specialized nature of UI Platform ownership, microfrontend expertise, and the "Staff" level designation, which implies significant technical leadership and impact. Data points considered include industry salary surveys for senior software engineers in Poland and general tech salary benchmarks for similar roles in comparable European markets. The specific range can fluctuate based on the candidate's precise experience, interview performance, and the company's compensation philosophy.

Benefits:

  • Competitive salary and potential for equity or stock options, common in growth-stage tech companies.

  • Comprehensive health insurance package, potentially including dental and vision.

  • Generous paid time off (PTO) and public holidays, aligned with Polish labor laws.

  • Opportunities for professional development, including conference attendance, training courses, and access to learning resources.

  • Flexible working hours and hybrid work arrangements to support work-life balance.

  • Potential for relocation assistance if applicable.

  • Access to modern office facilities in Warsaw, fostering collaboration and innovation.

  • Company-sponsored events and team-building activities.

  • Opportunities to work with cutting-edge AI tools and contribute to a forward-thinking product.

Working Hours: Standard full-time working hours are expected, typically around 40 hours per week, with flexibility to accommodate asynchronous collaboration across different time zones. Occasional work outside of standard hours may be required for critical deployments or on-call duties.

📝 Enhancement Note: Salary figures are estimates for Poland. Benefits are standard for tech roles in established startups and should be confirmed with Redpanda directly. The mention of equity is speculative but common for this level in growth-stage companies.

🎯 Team & Company Context

🏢 Company Culture

Industry: Redpanda operates in the data infrastructure and streaming platforms sector, with a strong focus on AI agent interaction and data governance. They are positioned at the intersection of real-time data streaming, AI technologies, and enterprise-grade control planes.

Company Size: Redpanda is a growth-stage startup, indicated by its focus on scaling products and teams. Company size is likely in the range of 100-500 employees, allowing for agile operations while building robust platforms.

Founded: Redpanda was founded in 2019, positioning it as a relatively young but rapidly evolving company in the competitive data infrastructure market.

Team Structure:

  • The UI Platform team is part of the broader engineering organization, likely reporting into a VP of Engineering or Head of Engineering.

  • This specific role is a hands-on individual contributor, leading through technical expertise and architectural guidance rather than direct management of a team.

  • Close collaboration is expected with product management, design, and other engineering teams responsible for individual product surfaces (e.g., Redpanda Streaming, Connect, SQL, Agentic Data Plane) and backend services. Methodology:

  • Redpanda emphasizes a modern, agile development approach, leveraging AI coding agents to accelerate implementation and improve developer productivity.

  • Data-driven decision-making is core, with a strong focus on observability, testing, and performance metrics for both the platform and the products built upon it.

  • Emphasis on establishing clear standards and best practices (e.g., through RFCs) to ensure consistency and maintainability across a distributed engineering organization.

  • A "people-first" culture is highlighted, focusing on trust, transparency, communication, and kindness.

Company Website: https://www.redpanda.com/

📝 Enhancement Note: Redpanda's positioning with AI agents and a unified control plane is a key differentiator. The culture described aligns with modern tech companies focused on innovation, collaboration, and developer experience.

📈 Career & Growth Analysis

Operations Career Level: This role represents a "Staff" level position within the frontend engineering discipline. It signifies a highly experienced individual contributor who is expected to drive significant technical direction, architectural decisions, and set technical standards across multiple product teams. The impact is broad, influencing how all frontend engineers at Redpanda work and how customer-facing products are built and maintained.

Reporting Structure: The Staff Software Engineer, UI Platform will likely report to a Director or VP of Engineering. While this is an individual contributor role, it requires strong collaboration with Engineering Managers, Product Managers, and other senior engineers who lead specific product teams.

Operations Impact: The UI Platform is the "front door" to all Redpanda Cloud services. Therefore, the stability, performance, scalability, and user experience of this platform directly impact customer acquisition, retention, and overall satisfaction. Decisions made by this role will have a direct influence on revenue generation (e.g., sign-up, billing, marketplace integrations) and the operational efficiency of the engineering teams building on the platform.

Growth Opportunities:

  • Technical Specialization: Deepen expertise in microfrontend architectures, UI platform design, and modern frontend tooling, potentially becoming a recognized authority in these areas.

  • Architectural Leadership: Transition into higher-level architectural roles, potentially leading platform engineering for broader domains or influencing technology strategy across the company.

  • Mentorship & Influence: Continue to mentor and uplift engineering talent across the organization, shaping the technical culture and best practices.

  • Cross-functional Exposure: Gain deeper insights into backend systems (Go, gRPC), data streaming technologies, and AI integration, broadening technical scope.

  • Startup Growth Trajectory: Participate in the scaling journey of a fast-growing startup, potentially taking on more responsibility as the company matures.

📝 Enhancement Note: The "Staff" title indicates a senior individual contributor path, focusing on technical leadership and broad impact rather than people management. Growth opportunities are geared towards deepening technical expertise and influencing engineering strategy.

🌐 Work Environment

Office Type: The role is based in Redpanda's growing Warsaw office, suggesting a hybrid work model. This implies a mix of in-office collaboration and remote work flexibility.

Office Location(s): The primary specified location is Warsaw, Poland. The company operates globally with teams in EMEA and the Americas.

Workspace Context:

  • The Warsaw office is described as "growing," suggesting a dynamic and evolving workspace.

  • Collaboration is key, with a need to work effectively with teams in different time zones (EMEA and Americas).

  • Access to modern tools and technologies, including AI coding agents, is a significant aspect of the work environment.

  • The environment likely fosters open communication and knowledge sharing, characteristic of agile, distributed teams.

Work Schedule: A standard full-time schedule of approximately 40 hours per week is expected. However, the nature of a global, distributed team and a critical platform role may necessitate some flexibility to accommodate cross-time zone meetings, urgent issues, and on-call responsibilities.

📝 Enhancement Note: The "Hybrid" status and specific office location in Warsaw are important for candidates to note. The emphasis on asynchronous communication suggests a structured approach to remote and distributed work.

📄 Application & Portfolio Review Process

Interview Process: The interview process is expected to be rigorous, typical for a Staff Engineer role in a growth-stage tech company. It will likely involve:

  • Initial Screening: A conversation with a recruiter to assess basic qualifications, experience, and cultural fit.

  • Technical Interviews: Multiple rounds focusing on:

    • Frontend Fundamentals: Deep dives into React, TypeScript, component architecture, state management, performance, and accessibility.
    • Microfrontend Architecture: Detailed discussions on Module Federation, host/remote contracts, dependency management, runtime issues, and migration strategies.
    • System Design & Architecture: Evaluating the candidate's ability to design complex, scalable systems, define technical standards, and plan large-scale migrations. This may involve whiteboard sessions or detailed architectural discussions.
    • Problem-Solving & Debugging: Scenarios assessing how the candidate approaches complex technical challenges and operational issues.
  • Portfolio Review/Case Study Presentation: A dedicated session where the candidate presents their portfolio, highlighting key projects, architectural decisions, and demonstrated impact, particularly related to platform ownership and microfrontend implementations.

  • Hiring Manager Interview: A discussion with the hiring manager to assess leadership potential, strategic thinking, and alignment with team goals.

  • Cross-functional Stakeholder Interviews: Conversations with peers from product, design, or other engineering teams to gauge collaboration skills and cross-functional impact.

  • Final Round/Executive Interview: Potentially a discussion with senior leadership to confirm overall fit and strategic alignment.

Portfolio Review Tips:

  • Focus on Impact: For each project, clearly articulate the problem, your role, the solution, and the tangible outcomes (e.g., improved performance, reduced development time, increased consistency, successful migration).

  • Highlight Platform Ownership: Emphasize projects where you were responsible for a shared component, framework, or platform, detailing the challenges of cross-team adoption and dependency management.

  • Showcase Microfrontend Expertise: If possible, include examples or detailed explanations of your experience with microfrontends, Module Federation, and the architectural considerations involved.

  • Demonstrate Architectural Vision: Present case studies that illustrate your ability to define architectural direction, set standards, and influence technical strategy.

  • Address AI Collaboration: Be prepared to discuss how you envision or have implemented AI tools in the development process, focusing on maintaining quality and consistency.

  • Structure for Clarity: Organize your portfolio logically, perhaps chronologically or by project type, with clear headings and concise descriptions. Be ready to walk through specific examples and answer in-depth questions.

Challenge Preparation:

  • System Design: Practice designing scalable frontend architectures, considering microservices, microfrontends, state management, and cross-team dependencies. Be ready to discuss trade-offs.

  • Migration Strategy: Prepare to outline a phased approach for migrating a monolithic UI to a microfrontend architecture, addressing potential challenges like data consistency, shared libraries, and team coordination.

  • Technical Standards: Think about how you would establish and enforce frontend standards, including processes for RFCs, code reviews, and design system evolution.

  • AI Integration: Consider how you would integrate AI coding agents into a complex platform development workflow, focusing on quality control, testing, and maintaining brand consistency.

📝 Enhancement Note: The interview process for a Staff Engineer will heavily scrutinize architectural thinking, leadership potential, and the ability to drive complex technical initiatives. A well-curated portfolio that directly addresses microfrontends and platform ownership is critical.

🛠 Tools & Technology Stack

Primary Tools:

  • React: The core JavaScript library for building user interfaces.

  • TypeScript: For static typing, enhancing code quality and maintainability in large applications.

  • Module Federation: A key technology for implementing microfrontend architecture, enabling dynamic code sharing and independent deployments.

  • Redpanda Cloud Platform: The overarching application environment managed by this role.

Analytics & Reporting:

  • Observability Tools: Likely candidates include tools like Datadog, Sentry, or custom solutions for monitoring application performance, errors, and user behavior.

  • Testing Frameworks: Comprehensive testing will be crucial, involving unit testing (e.g., Jest, Vitest), integration testing, and end-to-end testing (e.g., Cypress, Playwright).

  • CI/CD Pipelines: Experience with tools like GitHub Actions, GitLab CI, Jenkins, or similar for automating build, test, and deployment processes.

CRM & Automation:

  • Monorepo Tooling: Potentially Nx, Turborepo, or pnpm workspaces for managing a large codebase efficiently.

  • Bundlers: Vite, Rspack, or Webpack for optimizing frontend build processes.

  • Design System Tooling: Tools for managing design tokens, codegen, and visual regression testing (e.g., Figma integration).

  • Feature Flagging: Platforms like LaunchDarkly for controlled rollouts and A/B testing.

  • Frontend Delivery Platforms: Netlify or similar for hosting and deploying frontend applications.

📝 Enhancement Note: The technology stack is heavily focused on modern frontend development, microfrontend architecture, and robust development/deployment processes. Candidates should be prepared to discuss their experience with these specific technologies and their architectural implications.

👥 Team Culture & Values

Operations Values:

  • Innovation & AI Integration: A forward-thinking approach that embraces AI coding agents as a tool to enhance productivity and creativity, while ensuring quality and consistency.

  • Ownership & Accountability: Taking end-to-end responsibility for the UI platform, from architecture and development to operational health and user experience.

  • Collaboration & Transparency: Open communication and knowledge sharing across distributed teams, fostering trust and mutual respect.

  • Quality & Craftsmanship: A commitment to building robust, performant, accessible, and well-designed user interfaces, upholding high engineering standards.

  • Efficiency & Scalability: Designing systems and processes that can scale with the company's growth and optimize developer workflows.

Collaboration Style:

  • Cross-functional Integration: Working closely with product, design, and backend engineering teams to ensure seamless integration of features and API designs into the UI platform.

  • Standardization & Alignment: Driving consensus on architectural decisions and best practices through RFCs, design reviews, and code reviews, ensuring alignment across diverse product teams.

  • Knowledge Sharing: Actively participating in code reviews, design discussions, and documentation to share expertise and foster a learning environment.

  • Async-First Mindset: Proficient in asynchronous communication and collaboration, leveraging tools like GitHub for discussions and decision-making, while also being available for synchronous meetings across time zones.

📝 Enhancement Note: The emphasis on AI integration, ownership, and a people-first culture points to a modern, collaborative, and technically driven environment. Candidates should align their experiences with these values.

⚡ Challenges & Growth Opportunities

Challenges:

  • Microfrontend Migration Complexity: Successfully migrating multiple product surfaces to microfrontends while minimizing disruption, managing version compatibility, and ensuring consistent user experience across independently deployed modules.

  • Balancing Platform vs. Product Needs: Defining clear boundaries and contracts between the shared UI platform and individual product teams to enable autonomy without sacrificing consistency or introducing technical debt.

  • Scaling Design System for AI: Adapting the design system and component library to be effectively consumed by both human developers and AI coding agents, ensuring on-brand and accessible outputs.

  • Maintaining Operational Health: Ensuring the stability, performance, and reliability of a complex, composed UI platform, especially during high-traffic periods or when individual modules experience issues.

  • Cross-Time Zone Collaboration: Effectively leading and influencing teams distributed across EMEA and Americas time zones, requiring strong asynchronous communication skills and careful meeting scheduling.

Learning & Development Opportunities:

  • Deep Dive into Microfrontend Architectures: Becoming a subject matter expert in advanced microfrontend patterns, Module Federation internals, and strategies for managing complex composed applications.

  • AI-Assisted Development Best Practices: Gaining hands-on experience and shaping best practices for leveraging AI coding agents in large-scale frontend development.

  • Platform Engineering Expertise: Expanding knowledge in areas like build systems, CI/CD optimization, and frontend observability at scale.

  • Cross-Disciplinary Exposure: Understanding backend services (Go, gRPC) and data streaming technologies to better inform UI architectural decisions.

  • Leadership Through Influence: Developing skills in technical leadership, architectural governance, and mentoring without direct reports.

📝 Enhancement Note: The challenges presented are significant and require a seasoned engineer. The growth opportunities are substantial, offering a chance to shape a critical platform and gain expertise in emerging development paradigms.

💡 Interview Preparation

Strategy Questions:

  • Architectural Vision: "Describe your approach to designing and evolving a UI platform that supports multiple independent product teams. How would you define the host shell and remote contracts for Redpanda Cloud?"

    • Preparation: Focus on defining clear interfaces, versioning strategies, dependency management, and communication patterns. Illustrate with examples of how you've handled similar challenges.
  • Microfrontend Migration: "Outline a phased strategy for migrating Redpanda's existing UI to a microfrontend architecture using Module Federation. What are the key risks, and how would you mitigate them?"

    • Preparation: Detail phases (e.g., shared components, initial remotes, full migration), discuss data sharing, routing, shared dependencies, and strategies for minimizing downtime.
  • Technical Standards & Adoption: "How would you establish and drive adoption of frontend standards and a design system across multiple engineering teams, especially when working with AI coding agents?"

    • Preparation: Discuss RFC processes, code review guidelines, automated checks (linters, formatters), documentation, and how to make standards easy to adhere to or override when necessary.
  • Problem Solving & Debugging: "Imagine a critical bug is reported in a remote module that affects a core customer journey. How would you diagnose, resolve, and prevent recurrence of this issue in a microfrontend environment?"

    • Preparation: Detail your debugging methodology, including leveraging observability tools, isolating the issue to the remote module, coordinating with the product team, and implementing preventative measures (e.g., better testing, runtime checks). Company & Culture Questions:
  • "What excites you about Redpanda's mission and its approach to AI agents and data governance?"

    • Preparation: Research Redpanda's product, market position, and recent news. Connect your passion for challenging technical problems with their innovative solutions.
  • "How do you see yourself contributing to Redpanda's engineering culture, particularly in a hybrid, globally distributed team?"

    • Preparation: Highlight your experience with asynchronous communication, mentorship, and fostering collaboration.
  • "Describe a time you had to influence a team or stakeholder to adopt a new technology or architectural approach. What was your strategy, and what was the outcome?"

    • Preparation: Focus on communication, demonstrating value, and building consensus. Portfolio Presentation Strategy:
  • Structure for Impact: Organize your presentation around key projects that demonstrate your expertise in UI platform ownership, microfrontends, and architectural leadership.

  • Quantify Results: For each project, provide specific metrics and outcomes (e.g., "Reduced page load time by 30%," "Enabled 5 product teams to deploy independently," "Increased component reusability by 40%").

  • Tell a Story: Frame your projects as narratives: the problem, your role, the solution you architected and implemented, and the impact.

  • Address AI Integration: Be prepared to discuss how AI tools have influenced your work or how you envision them being integrated into the development lifecycle for this role.

  • Technical Depth: Be ready to dive deep into architectural decisions, trade-offs, and the technical challenges you overcame.

📝 Enhancement Note: Candidates should prepare to articulate their strategic thinking, architectural vision, and leadership capabilities, demonstrating how they can drive complex technical initiatives and positively influence engineering practices at Redpanda.

📌 Application Steps

To apply for this Staff Software Engineer, UI Platform position:

  • Submit your application through the provided link on jobs.ashbyhq.com.

  • Tailor your Resume: Highlight experience with React, TypeScript, microfrontend architectures (Module Federation), UI platform ownership, and leadership in driving technical standards. Quantify achievements with specific metrics.

  • Prepare Your Portfolio: Curate examples of past projects that showcase your architectural design skills, experience with shared platforms or libraries, and any work related to microfrontends or large-scale frontend systems. Be ready to present case studies demonstrating problem-solving and impact.

  • Research Redpanda: Understand their product offering, their focus on AI agents, and their company culture. This will help you articulate your interest and alignment during interviews.

  • Practice Technical & System Design Questions: Prepare to discuss complex frontend architecture, microfrontend strategies, and how you would approach building and scaling Redpanda's UI platform.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and industry-standard assumptions. All details should be verified directly with Redpanda Data before making application decisions.

Application Requirements

The role requires significant experience building production-grade web applications at scale using React and TypeScript, with deep expertise in microfrontend architectures. You must have a proven track record of leading large technical projects and driving architectural standards across distributed teams.