The vacancy is strong in responsibilities and requirements but lacks compensation details and company information.
Check Match — Just drop your CV
See your fit for Frontend Team Lead in seconds.
Overview
Join as a Frontend Team Lead to design and evolve a large Next.js application, lead a team of frontend engineers, and optimize web performance. Engineering (≈50%) - Design and evolve the architecture of a large Next.js (App Router) application: rendering strategy (SSR / SSG / ISR / RSC), code-splitting, and bundle health. - Drive web performance work end to end - Core Web Vitals (LCP, INP, CLS), edge caching, and RUM-based measurement. - Set the engineering standard through code review, pairing, and picking up the most complex or ambiguous tasks. - Own frontend observability: tracing, RUM, and the feedback loop from production back into engineering decisions. - Shape the CDN and caching strategy together with platform/infra (cache keys, Vary, surrogate keys, edge logic). Leadership (≈50%) - Lead, mentor, and grow a team of 4-6 frontend engineers (1:1s, growth plans, performance feedback). - Own delivery for the team: planning, prioritization, scoping, and realistic commitments. - Partner with product, design, backend, and DevOps on roadmap and technical trade-offs. - Improve how the team works: branching strategy, CI/CD, definition of done, release process. Tech stack - Core: TypeScript, React, Next.js (App Router), React Server Components. - Build / repo: pnpm monorepo, modern bundler tooling, shared internal packages. - Edge / delivery: Fastly CDN (VCL, edge caching, Early Hints), multi-brand / multi-tenant routing. - Observability: OpenTelemetry with a SigNoz backend, Web Vitals RUM pipeline. - Platform: Kubernetes-based deployments, object storage, Redis, MongoDB (backend-adjacent context). - Practices: trunk-based development, feature flags, strong SEO discipline for customer-facing pages.
Engineering (≈50%)
- •Design and evolve the architecture of a large Next.js (App Router) application: rendering strategy (SSR / SSG / ISR / RSC), code-splitting, and bundle health.
- •Drive web performance work end to end - Core Web Vitals (LCP, INP, CLS), edge caching, and RUM-based measurement.
- •Set the engineering standard through code review, pairing, and picking up the most complex or ambiguous tasks.
- •Own frontend observability: tracing, RUM, and the feedback loop from production back into engineering decisions.
- •Shape the CDN and caching strategy together with platform/infra (cache keys, Vary, surrogate keys, edge logic).
Leadership (≈50%)
- •Lead, mentor, and grow a team of 4-6 frontend engineers (1:1s, growth plans, performance feedback).
- •Own delivery for the team: planning, prioritization, scoping, and realistic commitments.
- •Partner with product, design, backend, and DevOps on roadmap and technical trade-offs.
- •Improve how the team works: branching strategy, CI/CD, definition of done, release process.
Conditions
- •20 vacation days and 5 family days yearly
- •Flexible start to the workday
- •Support from a professional corporate coach and psychologist
- •Regular internal and external activities, workshops, trips, and corporate events
- •Access to our internal knowledge base, meetups, and team-building activities
- •Ongoing training in new technologies and continuous professional development support
Nice to have
- •Experience with high-traffic, multi-brand or multi-tenant platforms.
- •Hands-on observability tooling (OpenTelemetry, SigNoz, or similar) and RUM.
- •Familiarity with Fastly or comparable CDNs at the VCL / edge-logic level.
- •SEO experience for large customer-facing sites (rendering, crawlability, hreflang, canonical strategy).