App Router, Server Actions, caching, middleware, SEO, ISR, Edge runtime, deployment.
Before starting, we run a 1-minute tech check — microphone, ambient noise, connection. If your setup isn't good enough, the test is fully refunded.
Prove you actually know Next.js App Router, Server Actions, and caching — not just that you listed it on your resume.
The Plume Next.js badge certifies your ability to architect, optimize, and ship applications with Vercel's React framework at an advanced level. In a 15-minute AI-led oral exam, you're questioned across the full Next.js stack: App Router anatomy (nested layouts, route groups, parallel routes, intercepting routes), rendering strategies (SSG, ISR, SSR, streaming with Suspense), the three-layer caching system (fetch cache, Full Route Cache, Router Cache), Server Actions, Edge middleware, technical SEO with the Metadata API, and deployment — including self-hosted Docker and Vercel-specific features like Edge Functions and distributed ISR. The exam covers Next.js 14 and 15, including Partial Prerendering, stable Turbopack, and the new 'use cache' directive.
Unlike a LinkedIn skill endorsement or a multiple-choice quiz, this is a live oral exam where you walk through real projects and real decisions. The AI examiner pushes back on vague answers — if you say 'I use ISR', it asks you to explain the revalidation window, what happens on a cache miss, and how you'd invalidate on-demand with revalidateTag. Claude Opus then reads the full transcript and produces a 0-100 score tied to concrete dimensions: technical accuracy, architectural reasoning, production experience, ecosystem knowledge, and communication clarity.
This badge is built for frontend and fullstack developers who use Next.js daily and want an objective, shareable proof of that mastery — whether for a freelance pitch, a job application, a technical interview, or simply an honest benchmark of where they stand on the latest versions of the framework.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Nested layouts, route groups, parallel and intercepting routes, loading.tsx, error.tsx boundaries and not-found handling. Ability to structure a production Next.js 14/15 project in a clean, maintainable way.
Deep understanding of the Server/Client Component boundary, Next.js-extended fetch, async Server Component patterns, and how to avoid request waterfalls by colocating or parallelizing data fetching.
Diagnosing and configuring all three cache layers: fetch cache (per-request memoization), Full Route Cache (server-side HTML and RSC payload), and Router Cache (client-side prefetch store). Using revalidatePath, revalidateTag, force-dynamic, and the Next.js 15 'use cache' directive.
Implementing Server Actions with server-side validation (Zod, valibot), error handling, optimistic updates on the client with useActionState, and knowing when to prefer a route handler (route.ts) over a Server Action.
Choosing between SSG, ISR, SSR, and streaming with Suspense based on data freshness, TTFB targets, and build-time constraints. Using generateStaticParams, Partial Prerendering, and Core Web Vitals as a feedback loop.
Writing Next.js middleware for auth gating, redirects, A/B testing, geolocation-based routing, and header injection. Understanding Edge runtime constraints (Web APIs only, no Node.js built-ins) and when to fall back to Node runtime.
Generating static and dynamic metadata with the Metadata API, sitemap.ts, robots.ts, OpenGraph and Twitter Cards. Controlling indexability, canonical URLs, and optimizing Time To First Byte for search engine crawlers.
Connecting Next.js with Prisma, Drizzle, NextAuth, Clerk, tRPC, or REST/GraphQL APIs. Deploying to Vercel (ISR, Edge Functions, Analytics) or self-hosted Docker, with observability via Sentry or OpenTelemetry.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Correctness and depth of answers about Next.js internals: cache lifecycle, Server Component rendering model, App Router behavior, Edge vs Node runtime differences, and how features like PPR work under the hood.
Ability to justify rendering strategy choices (SSG vs ISR vs SSR vs streaming), reason about data freshness vs performance tradeoffs, and design a scalable Next.js project structure for real production constraints.
Richness and authenticity of examples drawn from actual projects: caching bugs debugged, App Router migrations completed, performance incidents resolved, and complex stack integrations shipped.
Familiarity with the tools that surround Next.js in a real stack: ORMs, auth providers, deployment platforms, observability tools, and the ability to position Next.js objectively against Remix, Astro, Nuxt, or a Vite SPA.
Quality of spoken explanation: structuring answers logically, using precise Next.js vocabulary, and being able to simplify complex concepts without sacrificing technical accuracy.
A Plume session takes about 20 minutes, from tech check to badge delivery.
The AI confirms your mic is working and your environment is quiet. Nothing to install — everything runs in the browser. Keep your docs closed: the exam tests what you actually know, not what you can look up in 30 seconds.
The examiner asks you to introduce yourself briefly and describe your most representative Next.js project — stack, key decisions, App Router structure, what worked and what didn't. This calibrates the difficulty of what follows.
The core of the exam: 4 to 6 questions drawn from the calibrated themes — multi-layer caching, Server Actions, rendering strategy, Edge middleware, technical SEO, stack integration, Partial Prerendering, Next.js 15 changes. The AI follows up on your answers with targeted pushback on your specific technical choices.
The AI asks when you'd advise a client against Next.js and what you'd recommend instead. This tests maturity and the ability to think beyond framework loyalty — Remix, Astro, a Vite SPA, or Nuxt might all be right answers depending on the context.
Claude Opus analyzes the full transcript and produces your score (0-100), your level (Novice/Proficient/Advanced/Expert), and a detailed report. Your Next.js badge is ready immediately, with a shareable public URL.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You've followed Next.js tutorials and can create pages with the Pages Router or the basics of the App Router. You haven't shipped a production app and struggle to explain why a Server Component can't use useState, or the practical difference between SSR and SSG.
You use Next.js on real projects, you're comfortable with the App Router, you can configure fetch caching and implement basic Server Actions, and you've deployed to Vercel. Core rendering strategies are clear, but the three-layer cache system and PPR are still fuzzy.
You understand all three Next.js cache layers, you've migrated apps from Pages Router to App Router, you use revalidateTag in production, you write Edge middleware, and you integrate Next.js with complex stacks (Prisma, NextAuth, tRPC). You've kept up with Next.js 15 changes.
You make architectural decisions on high-traffic Next.js applications, you have hands-on experience with Partial Prerendering, Turbopack, and Edge vs Node runtime tradeoffs in production. You know when Next.js is the wrong tool and you mentor other developers on the framework.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You need to convince clients of your Next.js skills before they'll sign a contract. The badge gives you an objective, third-party proof point you can drop into your proposal or your profile on the spot — no take-home test required.
Next.js shows up in dozens of React job listings. A verified badge sets you apart from the candidates who simply typed 'Next.js' in their skills section and helps you pass technical recruiter filters before the first screening call.
You hire Next.js developers or need to benchmark your team's seniority. Taking the exam yourself gives you a calibrated reference point, and asking candidates to share their badge speeds up your technical assessment process.
You've been using Next.js for 6-12 months and want an honest read on where you stand on advanced topics like the cache system, PPR, Edge runtime, and Next.js 15. The oral exam surfaces real gaps better than any quiz.
You don't have a CS degree and want a concrete credential to back up your Next.js skills when applying for roles. A verified badge with a detailed report is a stronger signal than a GitHub repo most recruiters won't open.
Where and how your Next.js badge will help you day to day.
A potential client is choosing between two freelancers to rebuild their e-commerce platform in Next.js 14. You share your badge and the detailed report alongside your proposal — the decision goes your way without them needing to run a custom technical test.
Before a senior Next.js developer interview, you include your badge URL in your application email. The engineering team arrives already confident in your framework knowledge, so the interview focuses on product thinking and team fit instead of 'explain Server Components to me'.
You've just finished reading the Next.js 15 release notes and experimenting with Partial Prerendering. The AI exam reveals you have a strong grasp of hybrid rendering but are still conflating Router Cache and Full Route Cache — you know exactly what to study next.
You add your Next.js badge URL to the Certifications section of your LinkedIn profile and embed the Plume widget on your portfolio site. Recruiters searching for 'Next.js App Router' see a verified credential, not just a self-declared skill.
You're the CTO of a product startup and you ask Next.js developer candidates to share their badge before the final round. The detailed report helps you prepare targeted questions on the weak spots the AI identified — no more wasted time on basic screening.
You're a mid-level developer making the case for a senior title. Your Next.js badge at the Advanced or Expert level gives your manager an objective data point to support the promotion conversation, grounded in a third-party technical assessment.
A few minutes to check you have everything you need.
At the end of your session you don't just get a score — here's everything that awaits you.
You get a numeric score and a level (Novice, Proficient, Advanced, or Expert) that objectively reflects your mastery of App Router, Next.js caching, Server Actions, rendering strategies, and ecosystem knowledge.
Claude Opus produces a structured report that breaks down your strengths and gaps across each evaluated dimension — architecture, caching, rendering, ecosystem — so you know exactly what to tackle next if you want to level up.
Your oral session is securely stored and accessible only to you. Replay it to track your progress over time, or share it selectively if a recruiter or client wants to hear your reasoning directly.
A unique public URL lets you display your Next.js badge on LinkedIn, your portfolio, your GitHub profile, or in a job application email. The link shows your score and level in real time, no screenshot required.
Discover related skills you can validate with Plume.
A 15-min oral exam with an AI, a shareable badge for your recruiters.
Choose this badge · €19.99
