Memoization
Also written as useMemo, useCallback, React.memo
Remembering the result of an expensive calculation so it isn't repeated when the same input comes again. In React, useMemo, useCallback and React.memo use it to stop components re-rendering when nothing they depend on has changed; in coding interviews it's a classic dynamic-programming technique.
Think of it like
Writing the answer on the whiteboard so you don't redo the sum every time someone asks.
Junior or senior?
Junior sounds like
Wraps everything in useMemo 'for performance'.
Senior sounds like
Measured the slowdown first, for example with the React Profiler, and memoized only where it helped.
Ask them
“Tell me about a React performance problem you fixed. How did you find which component was re-rendering?”
Reading Memoization on a resume
- Common
- Memoization narrows the field but doesn't prove depth on its own. The junior-versus-senior contrast above is what separates one candidate from another.
Sourcing for Memoization
Every way it's written
("Memoization" OR "useMemo" OR "useCallback" OR "React.memo")Paste into LinkedIn Recruiter, Naukri or your ATS. Combine with a job title and location.
Job titles to search alongside it
Frontend Engineer · Frontend Developer · UI Engineer · Web Developer · UI Developer
Where this talent works in India — Frontend & Product Engineering
Target companies where the interface is the product — design-led consumer apps, developer tools, and SaaS with a real design-system practice. Service-shop frontend work rarely builds component-architecture depth.
For example: Adobe, Atlassian, Postman, CRED, Razorpay, BrowserStack, Freshworks, Zoho.