Frontend Frameworks

Framework interviews reward engineers who can trace data from user action to rendered UI. Strong answers name state ownership, render triggers, where side effects belong, and how server and client boundaries split responsibility.

This group spans React, Next.js, state management, and Vue/Nuxt/Angular stacks. Questions rarely stay on one API — interviewers connect hooks to list keys, routing to data loading, or global stores to component boundaries.

Checklist:

• Name the state owner before describing UI.
• Explain what triggers a render and why batching matters.
• Separate server rendering, client hydration, and client-only behavior.
• Use child domains for framework-specific depth.