0–2 years · Junior — React Native · JavaScript · Native modules · Offline storage · App release · Performance
Collects crash logs from users or analytics tools; reproduces the issue on different devices and scenarios; checks for common patterns in the reported crashes; reviews recent code changes or dependencies; isolates components that may be causing instability.
The crash logs indicate a memory leak. What steps would you take to identify and resolve this?
Specifies the performance issue and its impact on users; outlines the monitoring tools used to identify the problem; details the immediate actions taken to mitigate the issue; explains any long-term solutions implemented; reflects on lessons learned about performance testing pre-release.
What could you have done to catch it earlier?
Enables error boundaries to capture errors; reviews console logs for stack traces; uses React Native Debugger to inspect the application's state; isolates the issue by narrowing down to specific components; tests with different navigation libraries if applicable.
What if the logs don't provide enough information to identify the cause of the crash?
Confirms the bug fix is verified with test cases; updates versioning and changelog appropriately; performs regression testing to catch related issues; ensures that build configurations are set for production; prepares a rollout plan with monitoring for immediate feedback.
Once released, users report a new issue introduced by the hotfix. How do you handle this situation?
Analyzes the bundle size and checks for unnecessary imports; profiles the app startup to identify bottlenecks; reviews any synchronous code blocking the main thread; evaluates image sizes and loading methods; considers lazy loading for non-essential components.
After optimising, the load time improves but is still not ideal. What additional strategies could you implement?
Profiles the app using React Native Performance Monitor; checks for unnecessary re-renders by using React.memo or PureComponent; considers optimising the FlatList component by using getItemLayout; verifies the use of native driver for animations; evaluates the performance of image loading and caching strategies.
If using FlatList didn't improve performance, what other rendering strategies could you apply?
Load six more — you will get questions you have not seen first.
Give me six more →Say your answer out loud before revealing. Reading the answer first feels like learning and is not.