Hiring a Next.js developer — whether a freelancer or an agency — is one of the highest-stakes decisions a non-technical founder makes. The wrong hire doesn't just waste money. It produces an unmaintainable codebase that costs three times as much to fix as it did to build wrong.
This guide gives you the exact framework to evaluate Next.js talent before you commit.
Why Next.js Specifically Matters
Not all React developers are Next.js developers. Next.js has evolved dramatically since its early days — the App Router, Server Components, Streaming, Edge Middleware, and the `next/image` and `next/font` optimization primitives require specific, current knowledge.
A developer who learned React in 2019 and claims "Next.js experience" may be building Pages Router patterns in an App Router world — producing slower, bloated applications that fight the framework instead of leveraging it.
**What you're actually evaluating:** Can they articulate *when* to use Server Components vs. Client Components? Do they understand the hydration boundary? Can they explain why `"use client"` at the top of a file has a performance cost?
Freelancer vs. Agency: The Real Trade-Off
**Freelancers** offer lower hourly rates and more direct communication. The risk: single point of failure. Illness, another project, or burnout can halt your entire product.
**Agencies** offer team redundancy, broader skillsets (frontend + backend + infrastructure), and more structured delivery processes. The risk: you're paying for overhead, and junior developers often do the actual work while seniors handle sales.
**The hybrid you actually want:** A small, senior-only team — 2 to 4 people — that operates with agency discipline but founder-level care. This is rarer than it sounds, but it exists.
The Five Questions That Reveal Everything
1. "Walk me through how you'd architect the data-fetching layer for a real-time SaaS dashboard in Next.js."
A strong answer involves Server Components for initial page load, Supabase Realtime or SWR/React Query for live updates, and a clear explanation of where data fetching happens vs. where state management lives. Weak answers default to "fetch everything client-side."
2. "How do you handle authentication and protected routes in the App Router?"
Look for: middleware-based route protection, session handling with cookies (not localStorage), and awareness of the Server Component / Client Component boundary. A common red flag: using `useEffect` to check auth state client-side on protected pages.
3. "What's your process when a client's Lighthouse score is below 60?"
They should reach for `@next/bundle-analyzer` first, not guess. They should know the difference between LCP, CLS, and FID. They should prioritize `next/image` with proper `sizes` attributes, `next/font` for font optimization, and dynamic imports for heavy client-side components.
4. "How do you handle environment variable security across development and production?"
`NEXT_PUBLIC_` prefix variables are exposed to the browser — bundle them, and secrets leak. Non-prefixed variables stay server-side. A developer who doesn't know this distinction has almost certainly leaked API keys in a production build before.
5. "Show me the last three projects you've shipped."
Not demos. Not side projects. Live URLs, real traffic, real users. If they can't provide this, ask why.
The Red Flags That Predict Expensive Problems
- Uses `any` throughout TypeScript files ("it's just an MVP") - Keeps all logic in Client Components by default - Has no CI/CD setup in past projects - Can't explain what a database migration is - Proposes microservices for a pre-launch product
What a Strong Next.js Agency Engagement Looks Like
A competent agency will give you a fixed price (not just hourly), start with a written technical specification, maintain a private GitHub repository with daily commits, send weekly Loom demo updates, and hand over clean, documented code with an onboarding guide at project end.
Anything less is a risk you're absorbing, not them.
The Bottom Line
Hiring a Next.js developer is not primarily a technical decision — it's a trust decision. The technical assessment filters for competence. Your gut filters for fit. Both matter.
The cheapest hourly rate almost never produces the best ROI. The right developer or agency is the one who understands your *business* well enough to make the right technical trade-offs. That's rarer and worth more than any rate card suggests.
