What Next.js Developers Actually Build
Next.js shines for specific use cases. Here's what your Next.js developer will likely work on:
Marketing & Content Sites
Next.js's static generation makes it perfect for:
- Company websites - Fast-loading, SEO-optimized marketing pages
- Blogs & documentation - Markdown-based content with instant page loads
- Landing pages - A/B testable, performance-optimized conversion pages
Companies: Vercel, HashiCorp, Notion's marketing site
E-Commerce Platforms
Server-side rendering + static generation = perfect for commerce:
- Product pages - SEO-friendly with dynamic inventory
- Checkout flows - Secure server-side processing
- Personalized recommendations - Server components for fast, personalized content
Companies: Shopify storefronts, Target, Nike
SaaS Applications
The App Router makes complex apps manageable:
- Dashboards - Server components for data-heavy views
- Multi-tenant platforms - Dynamic routing with middleware
- Real-time features - Combined with WebSockets or Server-Sent Events
Companies: Cal.com, Linear's website, Supabase
Media & Entertainment
Performance-critical, high-traffic applications:
- Streaming platforms - Netflix's job portal uses Next.js
- Social media - TikTok's web experience
- News sites - The Washington Post, Hulu
The Next.js 13+ Paradigm Shift
Next.js 13 introduced the App Router, fundamentally changing how applications are built. This is crucial for hiring:
App Router vs Pages Router
- Pages Router (legacy): File-based routing in
/pages, client components by default - App Router (modern): File-based routing in
/app, server components by default
Most production apps still use Pages Router. Be clear about which your codebase uses.
Server Components
React Server Components (RSC) are the big change:
- Server Components: Render on server, zero client-side JavaScript
- Client Components: Interactive, run in browser (marked with 'use client')
A strong Next.js developer understands when to use each:
- Server: Data fetching, SEO content, database queries
- Client: Interactivity, browser APIs, state management
Data Fetching Patterns
The App Router changed data fetching completely:
// App Router - async components
async function ProductPage({ params }) {
const product = await getProduct(params.id); // Direct await!
return <ProductDetails product={product} />;
}
vs. the old Pages Router:
// Pages Router - getServerSideProps
export async function getServerSideProps(context) {
const product = await getProduct(context.params.id);
return { props: { product } };
}
Skills Assessment by Project Type
For Marketing/Content Sites
- Priority: Static generation, image optimization, SEO
- Interview signal: "How would you handle 10,000 blog posts without slow builds?"
- Red flag: Doesn't know about ISR (Incremental Static Regeneration)
For E-Commerce
- Priority: Caching strategies, middleware, edge functions
- Interview signal: "How do you handle personalized content with CDN caching?"
- Red flag: Would render everything on the server (performance nightmare)
For SaaS/Dashboards
- Priority: Server components, streaming, Suspense
- Interview signal: "When would you use a server vs client component?"
- Red flag: Adds 'use client' to everything (misses the point)
Common Hiring Mistakes
1. Not Specifying App Router vs Pages Router
These are significantly different. A developer expert in Pages Router needs time to learn App Router patterns. Be explicit about what your codebase uses.
2. Conflating Next.js with React
"Must know React" ≠ "Must know Next.js." React developers need to learn server-side patterns, caching, and deployment strategies specific to Next.js. Budget onboarding time.
3. Ignoring Deployment Knowledge
Next.js works best on Vercel but deploys anywhere. If you're on AWS, Docker, or other platforms, ensure candidates understand deployment nuances. Self-hosting Next.js has specific requirements.
4. Testing for Memorization
Don't ask "What's the difference between getStaticProps and getServerSideProps?" Ask "You're building a product page that needs real-time inventory but fast loads. Walk me through your approach."
Recruiter's Cheat Sheet
Questions That Reveal Expertise
| Question | Junior Answer | Senior Answer |
|---|---|---|
| "When do you use SSR vs SSG?" | "SSR is for dynamic, SSG is for static" | Explains trade-offs: SEO needs, caching, build times, revalidation strategies |
| "What are Server Components?" | "They render on the server" | Discusses zero-JS delivery, composition with Client Components, data fetching patterns |
| "How do you handle authentication?" | "There's a library for that" | Discusses middleware, edge functions, session strategies, security considerations |
Resume Green Flags
- Mentions App Router or Server Components (modern patterns)
- Performance metrics ("Improved LCP by 50%")
- Deployment experience (Vercel, AWS, Docker)
- Understanding of caching (ISR, CDN strategies)
Resume Red Flags
- Only Pages Router experience (needs upskilling)
- No mention of performance or SEO
- Lists Next.js but only built simple sites
- Can't explain the difference from plain React