Next.js portfolios are evolving
Hiring signals show Next.js 15 and React Server Components leading portfolio expectations — recruiters want SaaS dashboards, real‑time apps, and AI integrations (smart search, personalization) instead of simple blogs, plus server actions, edge functions, testing, and observability. Portfolios that explain tradeoffs between edge latency and centralized security are getting noticed. (youtube.com)
Next.js 15 was released on October 21, 2024 and its official changelog lists a new instrumentation.js API for server‑lifecycle observability as a stable feature. (nextjs.org) The Next.js docs for Server and Client Components were updated March 3, 2026 and state that layouts and pages are Server Components by default, enabling server data fetches and streaming to clients. (nextjs.org) Next.js’ testing guidance was refreshed in February 2026 with a Jest setup guide dated February 11, 2026 that explicitly notes Jest currently does not support async Server Components. (nextjs.org) Vercel’s Edge Runtime documentation specifies Edge Functions must begin sending a response within 25 seconds and may stream for up to 300 seconds, and Next.js docs document the Edge Runtime as a limited subset of Web APIs. (vercel.com) (nextjs.org) Sentry publishes official Next.js integration docs for error and performance monitoring, and the @sentry/nextjs npm package has continued releases, showing active ecosystem support for integrating observability into production apps. (docs.sentry.io) (npmjs.com) Industry hiring analyses show recruiters ramping AI tooling in 2025—SHRM cited a jump to 69% AI adoption in recruiting—and career guides from 2025–2026 recommend interactive, product‑style case studies (dashboards, demos, measurable metrics) over static screenshots. (pin.com) (dev.to) Multiple open starter kits and tutorials published in 2024–2026 use Next.js 15 to build AI‑enabled SaaS projects and semantic search demos—examples include a Next.js SaaS starter case study, a YouTube full‑stack AI portfolio tutorial, and Supabase’s Next.js vector‑search example. (thesaaspeople.com) (youtube.com) (supabase.com) Career resources and portfolio guides now advise documenting architecture tradeoffs explicitly (latency vs. centralization, edge vs. cloud) and offer step‑by‑step templates for communicating those decisions, while academic work published in January 2026 models the mobility/cost/performance tradeoffs of edge deployments. (resumly.ai) (arxiv.org)
