React Interview Questions and Answers: A Hiring Manager’s Guide (2026)
Technical interview guide · Updated November 2026
These React interview questions help you test real skill, not memorised definitions. They are grouped by junior, mid-level and senior roles. Each one shows what a strong answer covers, and the scorecard totals your ratings as you interview. Candidates can use the same list to prepare.
Short answer: good React interview questions ask candidates to explain trade-offs and real examples. Use six to eight questions matched to the level, add a short practical task, and score every candidate the same way.
How to Use These Questions
- Pick the level that matches the role: junior, mid-level or senior.
- Ask each question, then follow up with “why” and “what went wrong last time”.
- Score each answer from 0 to 3 in the scorecard below.
- Combine the score with a practical task and references before deciding.
Strong candidates explain trade-offs and give examples from real projects. Weak ones recite definitions.
React Interview Questions by Level
Filter by level, then score each answer. The scorecard adds up the total as you go. Your scores stay in your browser.
What is the difference between state and props?
A strong answer covers: Props come from the parent and are read-only. State belongs to the component, and changing it triggers a re-render.
Why do list items need keys?
A strong answer covers: Keys let React match items between renders. Stable, unique IDs work better than array indexes when order changes.
What does useEffect do, and what is the dependency array for?
A strong answer covers: Runs side effects after render. Dependencies control when it re-runs. A cleanup function prevents leaks.
What are controlled and uncontrolled components?
A strong answer covers: A controlled input keeps its value in React state. An uncontrolled input keeps it in the DOM and is read through a ref.
How do you prevent unnecessary re-renders?
A strong answer covers: Measures with the React Profiler first. Then memo, useMemo, useCallback, splitting components and keeping state close to where it is used.
How do you manage state in a large app?
A strong answer covers: Local state first and context for rarely changing global data. A store such as Redux Toolkit or Zustand, and TanStack Query for server data.
Explain custom hooks with an example.
A strong answer covers: Reusable stateful logic, such as useDebounce or useFetch. Follows the rules of hooks.
How do you test React components?
A strong answer covers: React Testing Library, testing behaviour rather than implementation, and mocked network calls. End-to-end tests with Playwright or Cypress.
What are React Server Components, and when do they help?
A strong answer covers: Components rendered on the server that send less JavaScript and can read data directly. Client components handle interactivity. Used in frameworks such as Next.js.
How would you speed up a slow React page?
A strong answer covers: Measures Core Web Vitals and profiles first. Code splitting, lazy loading, virtualised long lists, optimised images and a smaller bundle.
How do you approach accessibility?
A strong answer covers: Semantic HTML, labels, keyboard navigation and focus management. ARIA only when needed, plus automated and manual checks.
How do you structure a large React codebase?
A strong answer covers: Feature-based folders, a shared component library, TypeScript, lint rules and a clear data layer.
A Practical React Task
Ask the candidate to build a searchable, paginated list from a public API. It should have loading, empty and error states, plus one component test. Review it together afterwards.
Score the result on correctness, readability, tests and how clearly the candidate explains their choices.
Red Flags in a React Interview
- Puts all state in one global store by default
- Uses useEffect for logic that could be derived during render
- Ignores loading and error states
- Has no view on accessibility
Hire Vetted React Developers Without Running Every Interview
Staffenza runs this process for you. Every candidate passes five steps: CV and portfolio review, technical assessment, live technical interview, English check and references. You meet only the shortlist.
| Route | Staffenza fee |
|---|---|
| Remote staff augmentation from India or Pakistan | USD 225 a month on top of salary |
| Direct hire in the UAE or Saudi Arabia | 15–20% of the first-year package, with a 3-month replacement guarantee |
| Employer of Record in the UAE or Saudi Arabia | AED 899 per employee per month, plus government costs at actual cost |
The Bottom Line
Good React interview questions test reasoning, not memory. Use a few questions per level and probe with follow-ups. Pair them with a short practical task, and score every candidate the same way.
Want a shortlist of pre-vetted React developers? Send the role to [email protected] or use our contact page.
Related Guides and Tools
Browse all technical interview question guides.
React Interview FAQs
How many React interview questions should I ask?
Six to eight well-chosen questions are usually enough for one round. Go deep with follow-ups rather than covering every topic.
How long should a React technical interview be?
Plan about an hour for the conversation, plus a practical task. Keep the task short enough to respect the candidate’s time.
Should I use a take-home task or live coding?
A short take-home shows how someone works without pressure. Live pairing shows how they think and communicate. Some teams use a short version of both.
Can candidates use AI tools in a React interview?
Decide your policy and tell candidates in advance. If AI tools are allowed, ask them to explain every line they submit.
How does Staffenza vet React developers?
Every candidate goes through five steps: CV and portfolio review, technical assessment, live technical interview, English check and references. You then interview the shortlist yourself.


















