← Zettabyte Interview Insights

Zettabyte·Frontend Engineer·Technical Phone Screen·Senior

Senior
Apr 2026

Summary

Frontend engineer interview at Zettabyte that went deep on rendering strategy. One meaty question about SSR vs SSG vs CSR and when you'd actually pick each. Pretty technical for what felt like a system design screen.

Questions Asked (1)

Q1

How do you decide when to use server-side rendering versus static generation versus client-side rendering for a given page or application?

System DesignTechnical Trade-offs
Author's notes

This one sprawled in ways I didn't expect.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by framing the decision around user experience, data freshness, and performance budgets, then walk through the trade-offs of each rendering strategy. Use a concrete example from your experience to show how you evaluated and chose a hybrid approach.

Pro tip: Emphasize that most real-world apps use a mix of strategies per route, and mention that you measure Core Web Vitals and infrastructure costs to validate your choices—this shows you think beyond just technical implementation.

1. Clarify page requirements

Identify whether the page needs real-time data, personalization, or high interactivity, and how often content changes.

2. Evaluate rendering trade-offs

Compare SSR (fresh data, higher TTFB), SSG (fast, stale risk), and CSR (rich interactivity, poor SEO) against your requirements.

3. Consider performance and SEO

Prioritize SSG for static content, SSR for dynamic SEO-critical pages, and CSR for authenticated dashboards or highly interactive widgets.

4. Design a hybrid strategy

Combine strategies per route (e.g., SSG for marketing, SSR for product pages, CSR for user settings) and use incremental static regeneration where applicable.

5. Validate with metrics

Measure Core Web Vitals, server load, and build times, then iterate based on real user data and business goals.

Key Points to Mention

  • Trade-offs between TTFB, FCP, and TTI for each rendering method
  • SEO impact: SSR and SSG are better for crawlability than CSR
  • Data freshness requirements and caching strategies (e.g., ISR, stale-while-revalidate)
  • Infrastructure cost and scalability: SSG is cheapest, SSR requires server resources
  • User experience: CSR for highly interactive, authenticated areas; SSR/SSG for public-facing content
  • Hybrid approaches: Next.js, Nuxt, or similar frameworks allow per-page decisions

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.