Hiring Senior React/Next.js Engineers: Questions and Tasks
Senior React/Next.js hires shape scalability, velocity, and unit economics. The best engineers blend systems thinking, product sense, and measurable outcomes. Use the following questions and take-home tasks to separate framework users from end-to-end owners.
Behavioral signals of true seniority
- Owns outcomes: references Core Web Vitals, error budgets, and business metrics.
- Operates across the stack: schema design, CI/CD, edge trade-offs, observability.
- Builds leverage: patterns, docs, design systems, and mentoring.
Deep technical interview questions
- Next.js architecture: When do you prefer Server Components over Client Components, and how do you control caching with fetch options, revalidate, and cache tags? Look for nuanced trade-offs and examples using Route Handlers and streaming Suspense.
- Rendering strategy: Explain SSR vs ISR vs edge. When would you mark a route dynamic, or run on the Edge Runtime to reduce TTFB? Expect discussion of data source latency and consistency.
- Performance mastery: How do you prevent hydration waterfalls and reduce client JS? Great answers reference bundle analysis, dynamic import, image optimization, and Performance audits for web apps with RUM plus synthetic baselines.
- React concurrency: Describe useTransition and useDeferredValue in list UIs. What are the pitfalls with stale closures and memory leaks?
- State and data: Compare React Query, SWR, and server mutations. How do you invalidate with tag-based revalidation? Expect clarity on caching scopes and error boundaries.
- Type safety: How do you enforce end-to-end types using Zod or tRPC and protect API contracts during refactors?
- Security & auth: Walk through session management with NextAuth, CSRF, headers, and rate limiting. Ask about multitenant isolation and secrets hygiene.
- Testing: What deserves e2e in Playwright vs unit in Vitest? Look for contract tests with MSW and accessibility checks.
- Observability: How would you trace a slow request across server and client? Strong answers mention OpenTelemetry, Sentry, and Web Vitals events.
Take-home task A: Build for production, not the demo
Create a Next.js 14 App Router app: product catalog page, filterable, with server data.
- Architecture: Use Server Components by default, minimal client islands. Implement a Route Handler with streaming and Suspense fallbacks.
- Data and cache: Use fetch with revalidate and cache tags; add a revalidateTag endpoint for admin updates.
- Edge vs Node: Run read paths on Edge; justify with latency numbers. Provide a toggle to compare runtimes.
- Performance: Hit LCP under 2.5s on 4G; ship less than 120KB of client JS for the main route. Include a Lighthouse report and a short plan for Performance audits for web apps.
- Docs: A one-page decision record: trade-offs, metrics, and risks.
Take-home task B: Rescue a degraded app
We provide a repo with CLS and INP regressions, oversized bundles, and chatty API calls. Candidate must:
- Reduce CLS by fixing layout shifts with aspect-ratio and next/image sizes.
- Cut INP via input debouncing, virtualization, and useTransition.
- Drop bundle size 30% using dynamic import, shared component extraction, and fewer Client Components.
- Add tracing, Web Vitals reporting, and an incident playbook.
Live coding prompts (20-30 minutes)
- Implement optimistic updates with React Query and reconcile on server response, handling rollback on 409 conflicts.
- Write a typed Route Handler that validates input with Zod and returns streaming NDJSON.
- Fix a Suspense waterfall by moving data requirements to the server and collapsing providers.
Evaluation rubric
- Architecture and trade-offs (25%): Can articulate constraints and choose the simplest robust design.
- Performance and reliability (25%): Makes measurable promises; runs experiments; debugs with traces.
- Code quality and tests (20%): Readable, typed boundaries, fast tests.
- Product sense (15%): Understands impact on acquisition, SEO, and retention.
- Collaboration (15%): Communicates, documents, and mentors.
Advanced scenarios to probe
- SEO at scale: App Router metadata, sitemaps, canonical tags, and ISR invalidation for 1M pages.
- Internationalization: Middleware for locale detection, edge caches per region, and formatting costs.
- Cross-platform synergy: Share a design system and business logic with React Native; ask how they'd align web releases with React Native app development services and analytics.
Why this hiring bar maps to outcomes
Senior engineers think like Full-cycle product engineering owners: from discovery to delivery to growth. They select primitives that scale teams, not just pages. They operationalize Core Web Vitals, protect developer throughput, and tie PRs to revenue or risk reduction.
Where to find talent
If you need vetted specialists fast, slashdev.io pairs enterprises and startups with senior React/Next.js talent and complementary platform experts. Their network also covers data, backend, and mobile, making mixed squads effective from day one.
Adopt these tasks to reveal engineers who design for the edge, measure in production, and ship calmly at scale under real constraints.
