Senior React/Next.js hires should demonstrate systems thinking, product empathy, and battle-tested delivery. This guide gives enterprise-grade interview questions and take-home tasks that expose depth across performance, accessibility, GraphQL API development, and cross-functional execution-whether you recruit directly or through nearshore software development companies.

Focus your process on signal, not theater: design prompts that mirror production constraints, score consistently, and probe for decisions, trade-offs, and communication.

• React architecture: Explain when to use Server Components in Next.js 14 versus Client Components. What heuristics guide boundaries, and how do you avoid hydration waterfalls?
• Data fetching: Compare fetch in Server Actions, Route Handlers, and RSC, including caching, revalidation, and error boundaries. Provide code-level strategies to prevent overfetching.
• Performance: Diagnose a 5s TTFB on an edge-deployed Next.js app. Which measurements, profiling tools, and architectural fixes do you attempt first?
• State management: When would you prefer React Query over server-driven rendering? Describe cache invalidation for optimistic mutations with WebSocket or SSE updates.
• Security: Outline a defense-in-depth approach to auth in Next.js with middleware, HttpOnly cookies, CSRF, and permission checks in server-only modules.
• Accessibility: Walk through building a keyboard-first modal and verifying semantics with testing-library and axe. What are common anti-patterns?

• GraphQL API development: Propose a schema for a multi-tenant analytics app. Address authorization at the field level, connection pagination, and preventing N+1 queries.
• Client integration: Compare Apollo, Relay, and urql in a Next.js app router world. How do you implement SSR, persisted queries, and codegen for type safety?
• Caching: Outline a layered cache with CDN, GraphQL response caching, and entity-level normalization. When do you choose stale-while-revalidate versus hard invalidation?
• Edge and realtime: Design subscriptions via WebSocket on a serverless or edge runtime. How do you handle fan-out, backpressure, and fallbacks?

Use a single, production-like spec. Keep it small, but require judgment.

• Build a Next.js 14 app with the App Router, a dashboard page, and a details route. Implement Server Components for data display and a Client Component for a chart.
• Back the UI with a minimal GraphQL schema (Project, Report). Implement a Node resolver layer with dataloader to remove N+1, plus field-level authorization.
• Add SSR for the dashboard and a cached route handler for an export endpoint. Support revalidation with tags and handle errors with boundaries and logging.
• Demonstrate a11y: keyboard nav, focus traps, and visible states. Include tests with Vitest and testing-library; measure Lighthouse scores and explain trade-offs.
• Deliver a short architecture doc covering decisions, risks, and things you intentionally did not build.

Evaluation criteria: correctness, resilience, performance, a11y, readability, tests, and clarity of trade-offs. Cap scope to avoid weekend marathons; four hours should reach a thoughtful MVP.

Simulate production. Pair on a refactor of a tangled Client Component into a Server Component plus a small Client island. Assess reasoning, not memorization.

• Ask them to surface invariants, define contracts, and write tests first.
• Introduce a failing GraphQL resolver and watch their debugging workflow, logs, and hypotheses.
• Timebox a performance fix: remove a render loop, memoize selectors, and eliminate a waterfall with parallel data fetching.

Score 1-4 per dimension to enable consistent hiring across interviewers.

• Architecture: clear component boundaries, minimal coupling, and pragmatic use of Next.js features. Red flags: global state everywhere, custom routers, or ad hoc caching.
• Code quality: types first, tight naming, and tests that express behavior. Red flags: implicit any, flaky mocks, and heavy test coupling to implementation.
• GraphQL mastery: safe schema evolution, input validation, resolver batching, persisted queries, and cache strategies. Red flags: giant untyped any resolvers.
• Collaboration: concise async updates, crisp PRs, and empathy for design and ops. Red flags: defensive posture, vague comments, or ignoring product intent.

Nearshore software development companies can accelerate hiring by providing vetted full-stack engineers with overlapping time zones and strong English fluency.

• Insist on synchronous collaboration windows for pairing and incident response; verify via calendar artifacts, not promises.
• Run a culture screen: ask for a postmortem they authored and a tough stakeholder conversation they navigated.
• Validate remote readiness: network stability, secure workstation, and familiarity with PR etiquette and trunk-based development.

If you prefer a turnkey option, slashdev.io curates senior React, Next.js, and GraphQL talent and can embed specialized squads or act as a flexible software agency partner.

They provide excellent remote engineers and software agency expertise for business owners and startups to realize ambitious ideas without bloated overhead.

Before you extend an offer, run this checklist to de-risk delivery and accelerate onboarding.

• Reference calls probe for reliability under pressure and quality of collaboration.
• Security review of the take-home: secrets handling, dependency hygiene, and OWASP awareness.
• Onboarding.