React Developer interview questions
6 questions our recruiters use, with what a strong answer sounds like and a simple scorecard to compare candidates fairly.
Offices in San Jose, St. Petersburg, Algiers and Tunis
- Sourced and screened
- Employed through our EOR
- Paid locally, insured
The questions
When would you use useMemo or useCallback, and when would they make things worse?
What to listen for: Understands referential equality and re-renders, and says they measure before optimising instead of wrapping everything.
How do you decide what goes in global state versus local component state?
What to listen for: Keeps state as local as possible; separates server cache (React Query) from UI state; can explain a real refactor.
A page feels slow on mid-range phones. Walk me through how you would investigate.
What to listen for: Uses the React Profiler and Lighthouse, checks bundle size, large lists and unnecessary re-renders, and fixes the biggest cost first.
How do you make a custom dropdown accessible?
What to listen for: Mentions keyboard navigation, focus management, ARIA roles, and preferring native elements or a tested library.
Tell me about a component you built that other developers reused.
What to listen for: Thinks about API design, props, documentation and edge cases, not just the visuals.
How would you move a large app from JavaScript to TypeScript?
What to listen for: Incremental migration, strict mode by folder, typing API boundaries first; avoids a big-bang rewrite.
Questions to ask every candidate
- Walk me through the project you are proudest of. What exactly was your part?
- Tell me about a time you disagreed with a teammate or manager. What happened?
- How do you keep a remote team updated on your progress without being asked?
- What hours can you reliably overlap with a US team, and how do you handle async work?
- What would you want to have achieved in your first 90 days here?
A simple scorecard
Score each candidate 1 to 4 on role skills, problem solving, communication in English, ownership and remote work habits.
Agree on the bar before the first interview, and write scores down before discussing candidates. It reduces bias and speeds up decisions.
Skip the busywork. Let us hire your React Developer.
Free consultation, no commitment. Tell us what you need and we will tell you honestly whether we can help, and what it will cost.
Frequently asked questions
We hope these answers help you get a better understanding.
How many interview rounds should I run for a React developer?
Most startups do well with three: a 20–30 minute screen, a practical skills interview or work sample, and a final conversation about values and working style. More rounds tend to lose good candidates.
Can CKCODECONNECT run these interviews for me?
Yes. Our recruiters run screening and skills interviews and send you a short list of React developers with notes on each, so you only spend time on final interviews.
Related roles
Tell us about the React Developer you need
No commitment. A recruiter replies within one business day.
- A short list of vetted candidates
- Interviews and skills checks done for you
- Contracts, compliance and payroll handled
rami@ckcodeconnect.com
+1 (408) 915-8015
