Hiring Senior React/Next.js Engineers: Questions and Take-Home Tasks

Senior React/Next.js hires decide your roadmap speed, reliability, and SEO. For enterprise leaders evaluating nearshore software development companies or building internal teams of full-stack engineers, use the framework below. It focuses on production-grade decisions, GraphQL API development fluency, and the messy realities of shipping at scale.

Define “senior” by outcomes

• Turns fuzzy product goals into incremental, measurable deliveries.
• Owns performance, accessibility, and security budgets, not just “tickets.”
• Balances SSR/ISR/Suspense and server components tradeoffs in Next.js 13+.
• Communicates constraints clearly across design, backend, and marketing.
• Improves DevEx: testing, CI/CD, observability, and release discipline.

Deep-dive interview questions

• Next.js rendering strategy: “Walk me through choosing between SSR, SSG, ISR, and RSC for a marketing page with personalized CTAs and fast global TTFB.” Listen for cache keys, edge/CDN, hydration costs, and analytics implications.
• State management: “When do you prefer server mutations + cache invalidation over client stores?” Look for React Query/Apollo patterns, stale-while-revalidate, and optimistic updates.
• GraphQL API development: “Design a schema for a multi-tenant catalog with feature flags.” Expect discussion of node boundaries, pagination, N+1, federation, auth, and codegen.
• Performance: “How would you drop LCP from 3.2s to under 2.5s?” Seek concrete steps: critical CSS, Next/Image, preloading strategies, script priority, font loading, and profiling.
• Accessibility: “Audit a modal and fix keyboard traps and ARIA.” Seniors mention focus guards, inert backgrounds, and screen reader testing plans.
• Security: “Mitigate XSS in server components and client islands.” Expect CSP, escaping, strict types, and dependency review.
• Testing: “What deserves unit vs. integration vs. E2E?” Look for contract tests across the GraphQL boundary and realistic fixtures.
• Observability: “Which Web Vitals matter for SEO and how do you measure in CI?” Want answers referencing custom metrics, real user monitoring, and budgets in pull requests.

45-minute pairing prompt

Task: Refactor a Next.js page fetching products from a GraphQL endpoint into server components with streaming, loading skeletons, and error boundaries. Add a “quick add” cart interaction with optimistic updates. The repo includes failing tests and flaky API responses. Measure impact on TTFB and LCP.

What to watch: Thinking out loud, test-first triage, tracing logs, and principled rollback points. Senior engineers keep changes small, name tradeoffs, and wire observability as they code.

4-6 hour take-home (scoped for fairness)

Scenario: Build a feature flagged, localized product landing flow.

• Data: Consume a provided GraphQL schema; implement a minimal Node/Edge proxy to handle auth and rate limits. Bonus: persist cart server-side.
• Rendering: Use app router, choose SSR/ISR appropriately, and justify in a README. Implement incremental static regeneration for long-tail locales.
• Client: TypeScript, strict mode, form handling without heavy dependencies, and accessible components.
• Performance: Aim LCP ≤2.5s on a throttled profile. Include prefetch strategy, image sizing, and font loading rationale.
• Testing: Include unit, integration, and a smoke E2E. Provide contract tests against the GraphQL API using generated types.
• Analytics and SEO: Add structured data, canonical tags, and event tracking that does not regress Core Web Vitals.

Rubric (100 points)

• Architecture and rendering choices – 25
• GraphQL API development and data-layer correctness – 20
• Performance and accessibility budgets met – 20
• Testing depth and CI config – 15
• Developer empathy: docs, DX, and commit hygiene – 10
• Security posture and secrets handling – 10

Red flags to catch early

• Hand-wavy answers about hydration, caching, or server components.
• Overreliance on UI libraries with no accessibility verification.
• No strategy for pagination, cursors, and error handling across network seams.
• Ignores SEO mechanics, image policy, or internationalization constraints.
• Pushes giant PRs without measurable outcomes or rollback plans.

Signals of senior excellence

• Designs thin client layers over strong domain models and typed GraphQL.
• Speaks fluently about CDN strategy, cache invalidation, and edge rendering.
• Uses codegen, lints, and contracts to keep teams fast and safe.
• Aligns product, marketing, and engineering through explicit SLAs and budgets.

Working with nearshore software development companies

Nearshore teams can be phenomenal for React/Next.js velocity when you screen for alignment and overlap. Ask about release cadences, on-call models, and who owns Core Web Vitals. Demand examples where full-stack engineers partnered with backend teams to evolve GraphQL schemas rather than overfitting the client.

When evaluating vendors, run the same pairing and take-home process with a small, paid pilot. Hold them to the rubric, include security tabletop exercises, and confirm their incident response playbook. Great partners volunteer to prune scope, not expand it.

If you need a vetted bench quickly, slashdev.io can supply senior React/Next.js and full-stack engineers with battle-tested GraphQL experience, plus software agency leadership to shape roadmaps without slowing teams down.