Full Stack Senior Engineer (Frontend - Next.js)

Role Overview

Patrika's website is a high-traffic, mobile-first news runtime: breaking news means load spikes, Google Discover/News still matter, and Core Web Vitals are a traffic lever, not a vanity metric. This role is fullstack, but the weight sits on Next.js — App Router, RSC, ISR/edge caching, live feeds, SEO, and frontend observability. You still build the Frontend-for-Backend layer (API routes, server actions, typed contracts) against NestJS and WordPress. You will not just ship pages.

What You'll Work On

• Architect Next.js App Router + TypeScript applications using RSC to keep client JS small
• Core Web Vitals on mobile (LCP, CLS, INP) through breaking-news surges
• Live news feeds, homepage refresh, and cache/ISR/edge strategy (CDN, middleware, on-demand revalidation)
• Frontend-for-Backend: API routes, server actions, typed contracts to NestJS / CMS
• Design-system / reusable UI primitives that map to CMS content types
• SEO fundamentals: metadata, structured data, crawlable rendering
• RUM, profiling, and production error tracking so regressions are caught before users report them
• Collaborate with backend, DevOps, product, and editorial on publish → cache → page correctness

Who Is Right for This Role

• Production Next.js (App Router) and TypeScript, not Pages-router-only hobby work
• Has reduced mobile load time / JS bundle size with evidence
• Has designed ISR / edge / CDN caching that survived a real traffic spike
• Has built a live news (or similarly high-frequency) feed, not only static marketing pages
• Treats SEO and Core Web Vitals as part of the engineering job
• Can build the FFB layer — type-safe bridges between UI and APIs — not only CSS/React components
• Uses RUM/error tracking in production, not only local Lighthouse scores

Who Isn't a Fit

• React SPA experience with no Next.js rendering/caching/SEO ownership
• Has never been on the hook for Core Web Vitals or mobile load on a content site
• Cannot explain ISR, cache tagging, or on-demand revalidation against a CMS publish
• Frontend-only with no willingness to own API routes / server actions / contracts
• No experience with live or frequently updated content at traffic

How You'll Work

• This is a remote contract role.
• Works with backend, DevOps, SEO, and editorial; performance and Discover/News eligibility are shared outcomes.