The company needs a Frontend Architect to own the technical and business direction of its frontend ecosystem.
The role sits between engineering, product and management. You turn business vision and stakeholder requirements into clear technical direction and guide the development team to deliver it.
Each architectural decision is weighed for its business trade-offs so that it delivers the most value.
Responsibilities
Own the architecture across applications, shared libraries, design systems, build tooling and deployment pipelines.
Set and update frontend standards covering components, state, testing, performance budgets and accessibility.
Choose technologies and tools by weighing innovation, maintainability and total cost of ownership, and document your reasoning.
Understand the backend APIs, data models and event streams well enough to design the right frontend approach, and challenge contracts that do not serve the product.
Lead architecture reviews, proofs of concept and technical spikes for complex work.
Work with product owners and stakeholders to set and align frontend priorities.
Turn business goals into technical requirements, roadmaps and system designs.
Decide build versus buy and priorities based on business impact, time to market and long-term upkeep.
Translate management priorities into product and platform goals, and explain trade-offs to non-technical people in business terms.
Spot technical risks and opportunities early and include them in planning.
Guide teams through planning, estimates and delivery, splitting large initiatives into milestones.
Mentor senior and mid-level engineers through code reviews, design reviews and knowledge sharing.
Build a culture of quality, ownership and pragmatic engineering.
Work with backend architects, UX designers, product managers and DevOps to keep the whole system coherent.
Requirements
You bring 10+ years of professional software work, several of them in technical leadership roles such as architect, principal engineer or engineering lead.
You have designed and shipped large-scale, production frontend platforms used by real customers.
You have made decisions that carried both technical and business consequences.
You have expert knowledge of modern JavaScript and TypeScript and the browser, including rendering, the event loop, web APIs and the security model.
You have deep hands-on experience with React or Vue and clear views on when each fits. Familiarity with Next.js or Nuxt is expected.
You understand micro-frontends, module federation, monorepos (Nx, Turborepo), component-driven development and design systems.
You can manage state at scale with Redux, Zustand, signals or TanStack Query, and you know when to avoid them.
You handle performance work: Core Web Vitals, code splitting, lazy loading, caching, bundle analysis and SSR, SSG and ISR trade-offs.
You test across unit (Vitest or Jest), component (Testing Library) and end-to-end (Playwright or Cypress) levels.
You have a solid grasp of 3D on the web (WebGL, Three.js, WebGPU) and real-time streaming data UIs, which are central to our human-machine interfaces.
You treat WCAG accessibility and internationalization as core architecture concerns.
You are comfortable with Vite, Webpack, esbuild, CI/CD pipelines, feature flags and progressive rollouts.
You understand REST, WebSockets, WebRTC for real-time audio and video, gRPC, and message queues with event-driven design.
You can read, evaluate and negotiate API contracts such as OpenAPI, and design frontends that hold up as the backend changes.
You have working knowledge of OAuth2, OIDC, SSO, caching layers and CDN strategies.
You are familiar with AWS, Azure or GCP, Docker or Kubernetes, and observability tools for logging, tracing and RUM.
You communicate clearly in English, explaining technical topics to executives and business context to engineers. German is a plus.
You manage stakeholders well: you present options, back decisions with data and commit to a direction.
You are pragmatic and outcome-focused, seeing architecture as a means to business impact.
Experience in robotics, industrial automation, IoT or other hardware-adjacent domains is an extra.
Open-source contributions, technical writing or conference talks are an extra.
Experience scaling frontend teams and platforms through rapid company growth is an extra.