Justify static site generator vs CMS for a portfolio site

WHAT THIS TESTS: This question tests whether you can match infrastructure choices to actual workload characteristics rather than defaulting to familiar tools. The interviewer wants to see that you understand the trade-offs between static site generators and traditional content management systems, specifically around performance, security, maintenance overhead, and developer workflow. A portfolio of technical writing samples is inherently static, read-mostly content with a single author, so the ideal answer demonstrates cost-aware thinking and operational discipline.

A GOOD ANSWER COVERS: First, name a specific static site generator such as Hugo or Jekyll and pair it with a Git-based workflow for version control. Second, describe deployment through a static host or CDN so that content is served from edge locations with no server-side processing, following the eighty-twenty rule by getting most of the benefit with minimal operational work. Third, justify the rejection of a traditional CMS by citing the absence of runtime PHP, database queries, and plugin patching, which together remove per-request latency and eliminate entire classes of exploits. Fourth, acknowledge the limited scenarios where a CMS makes sense, such as multi-author workflows with non-technical editors or complex dynamic features, but clearly state those do not apply here. Fifth, mention concrete performance outcomes like faster time-to-first-byte and better search ranking potential due to speed.

COMMON WRONG ANSWERS: A major red flag is defaulting to WordPress or Drupal without acknowledging the maintenance tax. Another is claiming that static sites are only for developers and ignoring that modern Git-based workflows with markdown are accessible to most technical writers. Some candidates over-engineer by proposing containerized CMS instances or serverless databases for what is fundamentally a collection of HTML files. Others forget to mention security entirely or incorrectly assume that caching plugins make a dynamic CMS as fast as a static file served from a CDN.

LIKELY FOLLOW-UPS: The interviewer may ask how you would handle search functionality without a database, so be ready to discuss client-side search libraries or hosted search services like Algolia. They might also ask how a non-technical stakeholder could update content, which is an opportunity to mention headless CMS options or Git-based content editors. Another follow-up could involve scaling costs, where you should note that static hosting on platforms like Netlify or Cloudflare Pages is often free for low traffic, whereas a CMS requires ongoing compute and database spend.

ONE CONCRETE EXAMPLE: For a personal technical writing portfolio, I would use Hugo with the PaperMod theme, store markdown files in a GitHub repository, and deploy to Cloudflare Pages. New articles would be committed and pushed to main, triggering an automated build that generates HTML, CSS, and JavaScript. The resulting site would have no PHP runtime, no MySQL database, and no plugin ecosystem to patch, reducing the attack surface to zero while keeping time-to-first-byte under fifty milliseconds globally.