Senior Frontend Engineer (m/f/d)

Role Everything our users see runs on Next.js and React, and we'd like to hand it to you: the design system it's built from, how fast it loads, and whether everyone can actually use it. You'll work closely with our software architects, product owners, and fellow developers: code reviews, pair programming, and the technical decisions that stick around. Your mission You build and maintain our design system in React and Tailwind, so features stay consistent instead of being rebuilt from scratch each time. You own frontend performance in Next.js 16 — rendering strategy, bundle size, and what people actually experience on a mediocre connection. You treat accessibility as a default, not as cleanup at the end of the sprint. You develop the Node.js layer (Express.js, Nest.js) between the UI and our backend services, with Redis where caching helps. You push for clean code and automated testing, and you share what you know instead of sitting on it. You use coding agents as part of your daily workflow — directing their work, reviewing their output, and fixing what doesn't hold up. Writing code matters; knowing what good code looks like matters more. Your profile You've spent several years building production frontends with React, Next.js, and TypeScript. You know Tailwind CSS well and you've managed client-side state with Zustand. You test what you build — unit and component tests with Vitest, end-to-end tests with Playwright. You're comfortable in Node.js with Express.js or Nest.js, and working against APIs from a microservices backend. You work well in agile teams (Scrum/Kanban), you write clearly, and you're comfortable in English. You have a degree in Computer Science, Software Engineering, or a related field — or the experience that makes one unnecessary. Nice to have You've worked with AWS, Azure, or Google Cloud Platform. We're not in the cloud yet, so this is a plus, not a requirement. How you think We care as much about how you approach a problem as about which frameworks you know. You look past the edges of your own ticket: you notice when a fix really belongs in a different service, you question a process once it has stopped making sense, and you judge your work by whether the whole system got better — not by whether your part shipped. "Not my code" isn't a sentence we use much around here. Why us? You're joining at a point where the engineering foundations themselves are being rebuilt around AI-native workflows — not retrofitted onto legacy decisions, but designed now, while the architecture is still being shaped. That means you don't inherit someone else's five-year-old choices: you help make the calls on how services are split, where AI agents fit into the workflow, and what "good" looks like technically around here. Few Senior roles hand you this much real influence over the foundation rather than the features on top of it. On the practical side: 30 days of vacation, up to 50 workation days a year, a sabbatical option,…