Hiring Senior React/Next.js Engineers: Questions and Take-Home Tasks That Reveal Real Skill

Great senior React/Next.js engineers ship reliable features fast, align with full-cycle product engineering, and understand how frontends mesh with data, infra, and business goals. Use the following questions and tasks to separate resume-deep knowledge from production-grade judgment-while keeping a close eye on fair and transparent engineering rates and the realities of PostgreSQL and MySQL development in modern web stacks.

Skills Map to Anchor Your Process

• Next.js mastery: App Router, Server Components, static/ISR/SSR trade-offs, caching and revalidation.
• Performance: LCP/INP/TTFB budgets, bundle splitting, React concurrency, hydration strategies.
• TypeScript depth: strict mode, generics, type-safe API contracts, DX ergonomics.
• State/data: React Query/SWR, Server Actions, streaming, optimistic updates, error boundaries.
• Security: auth flows, session fixation prevention, CSRF, JWT rotation, CSP, SSRF hygiene.
• Accessibility and SEO: semantics, keyboard nav, aria patterns, structured data.
• Data fluency: pagination, indexing, transactions, and query tuning across PostgreSQL and MySQL development.
• DevOps: CI/CD, feature flags, observability, and cost-aware choices.

High-Signal Interview Questions (with Desired Depth)

• Next.js rendering: “Walk me through choosing between SSR, ISR, and static for a product page with inventory and pricing.” Look for answers referencing cache invalidation via tags, revalidatePath, edge vs node runtimes, and backpressure under traffic spikes.
• Hydration and streaming: “How would you avoid hydration mismatches with Server Components and client interactivity?” Expect discussion of use client boundaries, suspense, progressive rendering, and stable markup under conditional content.
• Data fetching: “Show how you’d prevent request waterfalls in a nested layout.” Strong answers: route-level prefetch, parallel Server Actions, batched queries, and profiling with React Profiler and Lighthouse traces.
• Auth and security: “Design a passkey + OAuth login in NextAuth (or custom) with session hardening.” Seek cookie flags, rotation strategies, CSRF protections on mutations, and rate limiting.
• Postgres/MySQL pragmatics: “Implement cursor-based pagination that works in both engines.” Candidates should discuss composite indexes, deterministic ordering (created_at, id), EXPLAIN/EXPLAIN ANALYZE, and phantom read avoidance via transactions.
• Edge and caching: “How do you cache personalized content safely at the CDN layer?” Expect Vary headers, key derivation, and separating public and user-specific fragments.
• Type safety: “Demonstrate an end-to-end typed contract.” Good signals: Zod or tRPC schemas, strict TS, and avoiding any in boundary layers.
• Operational maturity: “How do you measure the impact of a rendering change?” Look for synthetic and RUM metrics, error budgets, and experiment ramps.

System Design Prompt

“Design a multi-tenant analytics dashboard: real-time counters, heavy historical queries, and SEO-friendly marketing pages.” Strong candidates propose:

• Edge-rendered marketing (ISR) with incremental cache invalidation.
• Server Components for data-heavy widgets, streaming partial results.
• Partitioned tables and covering indexes in PostgreSQL; compatible schema or adapters for MySQL.
• Queue-backed writes to smooth spikes; read replicas for fan-out; cost-aware storage.
• Feature flags and circuit breakers to protect P95 latency.

Take-Home Task (4-6 hours, business-realistic)

Build a product listing app in Next.js (App Router) with the following:

• Server-rendered catalog page (ISR) with facet filters and pagination; product detail SSR with related items streamed.
• Admin mutation flow using Server Actions with optimistic UI and rollback.
• Cursor-based pagination that runs on PostgreSQL and MySQL; include schema, seed, and two query adapters.
• Performance budget: LCP < 2.0s on 4G Throttling; JS < 170KB initial; CLS ~0; include Web Vitals reports.
• Accessibility: keyboard flows, focus management, color contrast; axe clean.
• Security: secure cookies, CSRF on mutations, input validation with Zod, basic CSP.

Deliverables: repo, short architecture doc, Lighthouse and Web Vitals screenshots, EXPLAIN output for key queries, and a cost note comparing ISR vs SSR under peak traffic.

Scoring Rubric

• Architecture and trade-offs (25%)
• Performance and correctness (20%)
• Type safety, tests, and DX (15%)
• Data design and SQL quality (20%)
• Security and accessibility (20%)

Anti-Signals to Watch

• Defaulting to client-heavy pages without measuring cost or user impact.
• Pagination via OFFSET only; no stable ordering; no indexing rationale.
• Overusing Context for server state; ignoring cache invalidation.
• No plan for secrets, env segregation, or rollbacks.
• Hand-wavy performance claims without artifacts.

Fair and Transparent Engineering Rates

For senior talent, insist on clarity: a rate card tied to outcomes, not vanity hours; published multipliers for on-call, security review, and out-of-hours releases; costed options for SSR vs ISR and CDN usage; and a backlog framed in business terms. Vendors like slashdev.io can help you source vetted senior engineers and full-cycle product engineering teams with transparent pricing and the ability to plug into your stack quickly.

Mini Case Study: Signals of Excellence

We hired a candidate who cut LCP from 4.3s to 1.7s by moving hero media to CSS content-visibility and preloading critical fonts, replaced REST waterfalls with batched Server Actions, and introduced cursor pagination keyed by (created_at, id) with matching composite indexes. They instrumented real-user metrics, used EXPLAIN ANALYZE to drop query time from 120ms to 14ms in PostgreSQL, and demonstrated the same logic in MySQL with a slightly different index strategy. Result: 9% conversion lift and a 22% infra cost reduction after shifting 70% of catalog traffic to ISR.

Final Checklist

• Ask scenario-based questions that force trade-offs and metrics.
• Design tasks around realistic constraints, including PostgreSQL and MySQL development.
• Require artifacts: traces, EXPLAIN, Lighthouse, and a typed API surface.
• Score with a published rubric and maintain fair and transparent engineering rates.
• Consider a trial sprint with clear success criteria before long-term commitment.

Senior React/Next.js hiring succeeds when your process mirrors production: measurable, data-aware, and business-aligned. Calibrate for judgment, not trivia, and you’ll find builders who ship the right thing, the right way, at the right cost.