High React Question 207 of 229

When should you use useMemo and useCallback?

Frontend Master · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: REACT RENDER CYCLE

State changesetState / hook

ReconcileVirtual DOM diff

CommitUpdate real DOM

Simple meaning

useMemo caches an expensive calculated value between renders.

WHY — React instead of guessing?

Why interviewers care about React:

They are checking judgment

on React.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

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:

1
useMemo caches an expensive
calculated value between renders.
2
useCallback caches a function
reference so child memo components do not re-render for no reason.
3
I only add them
after measuring, because premature memoization adds noise.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“useCallback caches a function reference so child memo components do not re-rende”

Break into beats

useCallbackcachesafunctionreferenceso

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

useMemo caches an expensive calculated value between renders. useCallback caches a function reference so child memo components do not re-render for no reason.