React Developer mock interview questions
19 questions a React Developer panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. Hooks, rendering and component design rounds for React developer interviews.
Answer one real React Developer question now
A question a React Developer panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“A search component fetches results in a useEffect, and sometimes it shows results for an older query. Why, and how do you fix it?”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Thinking past the interview? Carmen can help with your whole React Developer career: a switch, a raise, or what comes next.
19 react developer mock interview questions
The questions a React Developer panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
A search component fetches results in a useEffect, and sometimes it shows results for an older query. Why, and how do you fix it?
Why they ask it: Race conditions in effects are a common React bug and a good test of effect cleanup.
A strong answer: Responses can return out of order, so an older slow request finishes after a newer one and overwrites its results. Fix by using the effect cleanup to ignore stale responses with a flag or cancel requests with an AbortController, or use a data fetching library that handles this. Debouncing the input reduces requests but does not fix the race on its own.
- 2.
What causes a React component to re-render, and when is that actually a problem?
Why they ask it: Tests the rendering model, which underlies most React performance questions.
A strong answer: A component re-renders when its state changes, when its parent re-renders, or when a context it uses changes. Re-rendering is usually cheap, and it is only a problem when rendering is expensive or happens very often. Measure with the React DevTools profiler first, then move state closer to where it is used, split context, or use memo, useMemo and useCallback where they prevent real work.
- 3.
When should you not use useEffect?
Why they ask it: Overusing effects is one of the most common patterns in weaker React code.
A strong answer: Do not use an effect to compute derived values from props or state, which can be calculated during render. Do not use one to respond to user events, which belong in event handlers. Do not use one to reset state when a prop changes, where a key can reset the component. Effects are for synchronising with external systems such as subscriptions, timers and non-React widgets.
- 4.
Why do list items need keys, and what goes wrong if you use the array index?
Why they ask it: Keys affect identity and state, which causes subtle bugs.
A strong answer: Keys tell React which item is which between renders. Using the index breaks when items are inserted, removed or reordered: state such as input values or expanded panels stays with the position rather than the item. Use a stable unique ID from the data.
- 5.
How do you decide where state should live, and when would you add a state management library?
Why they ask it: State architecture decisions shape how maintainable a React app is.
A strong answer: Keep state as local as possible and lift it only to the nearest common parent that needs it. Treat server data separately, using a data fetching and caching library rather than global state. Use context for values that rarely change, such as theme or current user. Add a client state library when many distant components update shared client state and prop passing or context becomes hard to manage.
- 6.
A server-rendered React page logs a hydration mismatch warning. What causes it and how do you fix it?
Why they ask it: Server rendering is common in React frameworks, and hydration issues are a frequent source of bugs.
A strong answer: The HTML rendered on the server differs from the first client render, often because of values like dates, random numbers, locale formatting, or checks for browser-only objects during render. Fix by making the first render deterministic, moving browser-only logic into an effect, or passing the same data to both. Invalid HTML nesting can also cause it.
- 7.
Tell me about a React codebase that was hard to work in. What made it hard and what did you do?
Why they ask it: Behavioural question about improving front-end architecture in practice.
A strong answer: The specific problems such as huge components, effects chaining into each other, prop drilling or inconsistent data fetching, the improvements you made such as extracting hooks, introducing a data fetching library or adding tests with Testing Library, and how you made the changes gradually without stopping feature work.
How the React Developer interview runs
Usually a recruiter screen, then a technical round on React specifically: rendering, hooks, state and effects. Most loops include a live coding session or take-home building a component that fetches data, handles loading and errors, and manages some interactive state. Later rounds cover performance, component architecture, server rendering if the team uses it, and how you test React code.
What the panel scores
Rendering and hooks
Whether you understand how React renders and how hooks work.
- Explains what triggers a re-render
- Uses effects only for external synchronisation
- Handles effect cleanup and race conditions
State architecture
Whether state is placed and managed sensibly.
- Keeps state local where possible
- Separates server data from client state
- Uses stable keys
Performance
Whether you improve performance based on measurement.
- Profiles before optimising
- Uses memoisation where it helps
- Understands hydration and server rendering
Code quality and testing
Whether components are maintainable and tested.
- Writes small, focused components
- Tests behaviour through the UI
- Improves codebases incrementally
Common questions in every interview
These come up in almost every React Developer interview regardless of the company or the round.
- 8.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 9.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 10.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 11.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 12.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 13.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 14.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 15.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 16.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 17.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 18.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 19.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Every round ends in a scorecard like this
Your React Developer answers, quoted back, scored on what this role is judged on, with the line to say instead.
Real screen from the app. Sample from a product design round.
Related roles
All Engineering →No spam. Unsubscribe anytime.
Ready to practice as a React Developer?
Sign up free, no card. 30 voice minutes and unlimited typed interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 888+ roles to choose from
Questions & answers
- Is the React Developer mock interview free?
- Yes. 30 voice minutes and unlimited typed React Developer interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic React Developer job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a React Developer job description first, then practice the interview with the same JD for a tighter loop.