What are the benefits of Static Site Generation in Next.js?

0-2 years experience

1. 1If you need to add a new marketing page to our Next.js site, would you choose getStaticProps or getServerSideProps? Explain why.
2. 2What happens to the page load time when we switch a page from client‑side rendering to static generation?
3. 3How would you pre‑render a product detail page that doesn’t change often using Next.js?

2-5 years experience

1. 1We noticed the homepage load time increased after moving some data fetching to getServerSideProps. How would you refactor it using SSG, and what trade‑offs should you consider?
2. 2During a deployment, a static page fails to update after content changes in the CMS. Walk me through how you would debug the issue.
3. 3Explain why enabling incremental static regeneration might be preferable to full rebuilds for a blog with thousands of posts.

5-8 years experience

1. 1Our e‑commerce site serves millions of users and uses a mix of SSG and SSR. How would you decide which pages to generate statically, and what caching strategies would you employ to keep data fresh without hurting performance?
2. 2Design a fallback strategy for a Next.js app that uses SSG for most pages but must handle occasional user‑specific data. How would you avoid blocking the build and still deliver personalized content?
3. 3What are the edge cases where SSG could actually degrade SEO or performance, and how would you mitigate them at scale?

8+ years experience

1. 1We are planning to migrate a legacy monolith to a micro‑frontend architecture using Next.js with SSG as the default rendering mode. What architectural considerations and cross‑team processes would you put in place to ensure a smooth migration and long‑term maintainability?
2. 2How would you set up a CI/CD pipeline that automatically decides between static generation and server‑side rendering for new routes, balancing developer velocity and operational cost across multiple product teams?
3. 3Discuss the long‑term implications of relying heavily on static generation for a SaaS platform that expects frequent feature toggles and A/B testing. How would you structure the codebase and deployment workflow to accommodate rapid experiments without rebuilding the entire site each time?