What causes hydration errors with dates or random IDs?
PICTURE THIS: DOM IS A TREE
Simple meaning
Server and client format Date differently by timezone, or I generate Math.random in render.
WHY — Next.js instead of guessing?
Why interviewers care about Next.js:
who only read docs from people who shipped.
and tied to Frontend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Server and client format
Date differently by timezone, or I generate Math.random in render.
- 2I format dates in
useEffect, pass an ISO string from the server, or use suppressHydrationWarning only for a tiny known mismatch.
- 3Stable ids should come
from the data layer.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Server and client format Date differently by timezone, or I generate Math.random in render. I format dates in useEffect, pass an ISO string from the server, or use suppressHydrationWarning only for a tiny known mismatch.