Technical screening questions
Ask for one example per question and listen for specifics.
- How does React Native differ from native development? A good answer: JavaScript layer with a bridge or new architecture to native views.
- When do you write a native module? A good answer: For platform features without a library.
- How do you handle navigation and state? A good answer: React Navigation and a store.
- How do you debug performance? A good answer: Profiling, list virtualization and avoiding re-renders.
- How have you released an app? A good answer: Signing, review and rollout on both stores.
Quick screening questions
Use these when you have only a few minutes.
- Which apps did you ship and on which stores?
- When do you drop into native code?
- How do you handle performance on long lists?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds screens.
- Mid: owns features and releases.
- Senior: sets architecture and native integration.
Red flags
Any of these is a reason to probe further.
- Web React only.
- No published app.
- Cannot discuss native tooling.
Tools you should hear mentioned
A React Native developer with real experience usually names several of these without prompting.
- React Native
- TypeScript
- Redux or similar
- Expo or bare workflow
- Xcode and Android Studio
- Jest
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a React Native developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.