Hiring Guide: Interview Questions and Take-Home Tasks for Senior React/Next.js Engineers
Senior React/Next.js hires have outsized impact: they shape architecture, speed up delivery, and prevent costly rewrites. Below is a battle-tested process with enterprise-grade questions, calibrated scoring, and realistic take-home tasks that surface signal fast-especially for static site generation experts and teams scaling complex apps.
Role Calibration and Must-Haves
Define the problem space first. Are you migrating from Create React App to Next.js 14 with App Router? Running multi-tenant, high-traffic sites with ISR? List must-haves: TypeScript, SSR/SSG/ISR fluency, performance budgets, testing discipline, and CI/CD literacy across Vercel, AWS, or hybrid.
Deep-Dive Interview Questions (with What "Great" Looks Like)
- Data fetching strategy: When do you choose SSG, SSR, ISR, or client fetch? Great: answers with cache invalidation timelines, fallback modes, revalidation tags, and cost trade-offs at scale.
- Routing and layouts: Explain parallel routes and intercepting routes in App Router. Great: concrete migration plan from pages/ to app/, guarding partial renders with Suspense boundaries.
- State management: When to pick server components, React Query, or context? Great: prefers server-first data, uses query caching keys, minimizes client bundles, isolates mutation side effects.
- Performance: Diagnose a 2.5s TTFB on SSR pages. Great: correlates to cold starts, N+1 DB calls, slow edge configs; proposes streaming, prefetching, and route segment caching.
- Security: How do you harden NextAuth or custom JWT flows? Great: httpOnly cookies, rotating refresh tokens, CSRF on mutations, header-based validation at the edge.
- Accessibility and SEO: Tackle Core Web Vitals and structured data. Great: uses semantic roles, prefers native elements, implements JSON-LD, image alt policies, and font loading strategies.
- Testing: What to snapshot, unit, integration, and E2E? Great: contracts on server actions, component tests for render logic, Playwright for critical user flows with network mocking.
System Design and Architecture Signals
Prompt: "Design a platform hosting 500 marketing sites, each customizable, with real-time content previews." Look for multi-tenant SSG with per-tenant revalidation, shared component libraries, i18n routing, access control on previews, and cost-aware asset pipelines.
Pair Programming Exercise (30-40 minutes)
Provide a small Next.js repo with a slow product listing. Ask them to: add server components for listings, implement route segment caching, replace client data fetching with fetch cache tags, and fix render waterfalls with Suspense. Observe commit hygiene and incremental refactors.
Take-Home Task (4-6 hours, enterprise-realistic)
Spec: Build a Next.js 14 store-front with SSG for category pages, SSR for product detail, and an admin-only "revalidate tag" endpoint. Include pagination, breadcrumb schema, and a-lighthouse budget. Bonus: Edge middleware for geo-redirects, Postgres schema with migration script, and a canary deploy plan.
Submission expectations:
- Architecture doc explaining data ownership, cache strategy, and fallback behavior for ISR.
- Typed APIs: zod or TypeScript interfaces shared client/server; strict tsconfig.
- Testing: unit for utilities, integration around server actions, and 2 Playwright specs.
- DX: precommit linting, turborepo or pnpm workspaces if monorepo is justified.
Evaluation Rubric
- Impact over cleverness: uses primitives that minimize ops overhead and cognitive load.
- Scalability: designs for thousands of pages, batched revalidation, and image/CDN policy.
- Observability: adds logging, metrics, and trace IDs around server actions and cache hits.
- Security posture: secrets management, audit trails, and least-privilege environments.
- Communication: crisp trade-off narratives; risks, mitigations, and next steps documented.
Red Flags to Catch Early
- Defaulting to client components without measuring bundle impact.
- Confusing ISR with client-side caching or assuming revalidate equals real-time.
- No strategy for schema evolution or feature flags during phased rollouts.
- Poor understanding of CDN behavior, stale-while-revalidate, or cache busting.
Cross-Discipline Fit
Great seniors collaborate beyond web. If your organization also needs iOS app development services, probe synchronization patterns: shared GraphQL schemas, event-driven backends, and design token pipelines feeding both web and native. Polyglot empathy prevents platform drift.
Build vs. Buy: Talent Sourcing
Time is money at enterprise scale. Hire vetted senior software engineers who have shipped revenue-critical Next.js systems, not just demo apps. Partners like slashdev.io vet for outcomes and provide remote specialists-from React leaders to static site generation experts-plus advisory muscle for architecture and delivery.
Case Study Scenarios
- Global catalog: 2M SKUs, hourly price changes. Solution: SSG categories with periodic revalidation, SSR product detail with edge caching, and Kafka-driven tag invalidation.
- Newsroom: 1,000 writers, instant publish. Solution: SSR for breaking pages, on-demand revalidate for recirculation modules, streamed comments via server actions.
- B2B dashboard: strict SLAs. Solution: server-first data, optimistic mutations with rollback, feature flags, and observability baked into route handlers.
Offer Closing and Onboarding
Sell impact: ownership of performance budgets, space to refactor toward server components, and a runway to standardize design systems. First steps: profile ruthlessly.
