<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shashank Rai on Medium]]></title>
        <description><![CDATA[Stories by Shashank Rai on Medium]]></description>
        <link>https://medium.com/@shashankrai01?source=rss-a4c35d107f51------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dL7dVhgEsr0HzJFDbFFpzw.png</url>
            <title>Stories by Shashank Rai on Medium</title>
            <link>https://medium.com/@shashankrai01?source=rss-a4c35d107f51------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:07:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shashankrai01/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[IntraEdge React Native + GraphQL Role Interview Experience]]></title>
            <link>https://medium.com/@shashankrai01/intraedge-react-native-graphql-role-interview-experience-f55b02e93daa?source=rss-a4c35d107f51------2</link>
            <guid isPermaLink="false">https://medium.com/p/f55b02e93daa</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Shashank Rai]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 11:51:45 GMT</pubDate>
            <atom:updated>2026-08-09T11:55:56.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="IntraEdge logo" src="https://cdn-images-1.medium.com/max/200/1*bDpI-g3YXplRSfHUA--iAw.jpeg" /></figure><p>Recently, I interviewed for a <strong>React Native + GraphQL Developer</strong> role at <strong>IntraEdge</strong>.</p><p>Going into the interview, I expected the usual React Native questions.</p><p>But the interview covered a much broader mix of <strong>JavaScript fundamentals, React concepts, TypeScript, GraphQL, performance, and mobile CI/CD</strong>.</p><p>Here’s what came up.</p><h3>Round 1 — React Native, React &amp; JavaScript</h3><p>The first round started with coding and gradually moved into React and JavaScript concepts.</p><p><strong>1. Can you find the second-largest number in an array without sorting?</strong></p><p>A simple-looking question, but there are multiple edge cases an interviewer can explore once you start discussing your approach.</p><p><strong>2. Can you implement a Higher-Order Component (HOC)?</strong></p><p>And naturally, this led to the bigger question:</p><p><strong>When would you actually use an HOC in a React application?</strong></p><p><strong>3. What is the difference between </strong><strong>useCallback and </strong><strong>useMemo?</strong></p><p>And more importantly:</p><p><strong>When should you actually use them?</strong></p><p><strong>4. Can you explain how React decides when a component should re-render?</strong></p><p>Then came the fundamentals.</p><p><strong>5. How well do you know JavaScript beyond React?</strong></p><p>The discussion covered JavaScript fundamentals and concepts that every frontend developer should be comfortable with.</p><p><strong>6. What is debouncing?</strong></p><p>Followed by the practical question:</p><p><strong>Where would you use debouncing in a real application?</strong></p><p>And then:</p><p><strong>Can you implement it? Asked to implement in online editor.</strong></p><p><strong>7. How would you design a CI/CD pipeline for a React Native application?</strong></p><p>Not just building the application.</p><p>Think about the entire journey:</p><p><strong>Code → Test → Build → Sign → Distribute → Release</strong></p><p>How would you automate it?</p><h3>Round 2 — TypeScript, GraphQL &amp; React Native</h3><p>The second round moved deeper into the technologies mentioned in the job description.</p><p><strong>1. </strong><strong>type vs </strong><strong>interface — what&#39;s the difference?</strong></p><p>Then came:</p><p><strong>2. What is </strong><strong>Partial and when would you use it?</strong></p><p><strong>3. What is </strong><strong>Omit and when would you use it?</strong></p><p>I was asked to write their syntaxes. These are the kinds of TypeScript questions that look straightforward until the interviewer starts asking about real-world use cases.</p><p>Since GraphQL was a major part of the role, this section went deeper.</p><p><strong>4. What is GraphQL and how is it different from REST?</strong></p><p><strong>5. What are queries and mutations in GraphQL?</strong></p><p><strong>6. Can you write a GraphQL query?</strong></p><p><strong>7. Can you write a GraphQL mutation?</strong></p><p>I was asked to write their syntaxes as well. Simple questions on paper — but being able to explain how you’ve actually used them in an application makes a big difference.</p><p>And then came one of the most important React Native topics:</p><p><strong>8. How would you optimise a </strong><strong>FlatList?</strong></p><p>This is one of those questions where the interviewer can keep digging:</p><ul><li>What causes poor list performance?</li><li>What would you check first?</li><li>Which optimizations would you apply?</li></ul><p>And when would you consider something other than FlatList?</p><p><strong>9. How can you pass data between React components?</strong></p><p>Depending on the component relationship, there are several approaches.</p><p>Which one would you choose — and why?</p><p><strong>10. How would you implement data sharing using the Context API?</strong></p><p>And the natural follow-up:</p><p><strong>When would you use Context, and when would you choose another state-management approach?</strong></p><h3>My Takeaway —</h3><p>Overall, I found this to be a <strong>well-balanced interview</strong>.</p><p>It wasn’t just:</p><blockquote><em>“How much React Native do you know?”</em></blockquote><p>Instead, it tested different layers of frontend engineering:</p><p><strong>JavaScript → React → React Native → TypeScript → GraphQL → Performance → CI/CD</strong></p><p>And I think that’s exactly what makes a technical interview valuable.</p><p>For React Native developers preparing for similar roles, I’d definitely recommend brushing up on the fundamentals instead of focusing only on framework-specific APIs.</p><p>Because at some point, the interviewer stops asking:</p><p><strong>“Do you know React Native?”</strong></p><p>and starts asking:</p><p><strong>“Do you understand software engineering?”</strong></p><p>If you’re preparing for a <strong>React Native interviews</strong>, save this list. You might see a few of these questions in your next interview.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f55b02e93daa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deloitte Senior Frontend Developer (React.js & Next.js) Interview Experience]]></title>
            <link>https://medium.com/@shashankrai01/deloitte-senior-frontend-developer-react-js-next-js-interview-experience-8a9acf9f2d53?source=rss-a4c35d107f51------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a9acf9f2d53</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[interview-experience]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Shashank Rai]]></dc:creator>
            <pubDate>Mon, 03 Aug 2026 06:31:01 GMT</pubDate>
            <atom:updated>2026-08-03T06:31:01.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Deloitte Logo" src="https://cdn-images-1.medium.com/max/1024/1*rOqG0xHRyB1DyDJPCvkySQ.png" /></figure><p>I recently appeared for the Senior Frontend Developer interview at <strong>Deloitte</strong> for a React.js and Next.js role. The interview was primarily focused on frontend fundamentals, React ecosystem concepts, performance optimisation, accessibility, testing, and problem-solving. All the shared questions are from <strong>Round 1 only</strong>.</p><p>One interesting thing about the interview was that it started with questions around Angular. I mentioned that I don’t have hands-on experience with Angular and that my experience is primarily with React.js and Next.js. The interviewer was perfectly fine with that and immediately shifted the discussion towards my area of expertise.</p><p>The overall interview was quite conversational. Most questions were followed by multiple probing questions to understand not just whether I knew a concept, but also when and why I would use it in real-world applications.</p><h3>JavaScript &amp; CSS</h3><p>The interview began with some fundamental JavaScript and CSS questions.</p><p>Some of the questions included:</p><ul><li>How would you center a div without using display properties?</li><li>Explain the differences between forEach, map, filter, and reduce.</li></ul><p>There was also a coding question where I had to check whether two strings are anagrams of each other without using built-in methods such as sort() or join(). The interviewer was more interested in understanding the approach, time complexity, and handling edge cases rather than simply arriving at the correct answer.</p><h3>React.js &amp; Next.js</h3><p>A significant portion of the interview revolved around React and Next.js concepts.</p><p>Some of the questions asked were:</p><ul><li>How would you efficiently render a large list of data without pagination?</li><li>What are the different hooks you’ve used in React?</li><li>useCallback vs useMemo — when would you use each of them?</li><li>Why and when should we create custom hooks?</li><li>What are the differences between setState and useState?</li><li>If a custom hook contains two useEffect hooks (one with an empty dependency array and another with dependencies), when will they execute if the component re-renders?</li><li>How would you pass data from a child component to its parent?</li><li>How was this achieved before forwardRef?</li><li>What are the different ways of passing data between components?</li><li>What are hydration issues in React and how would you fix them?</li><li>Explain dynamic routing in Next.js.</li></ul><p>The interviewer frequently asked follow-up questions based on my answers. For example, when discussing rendering large lists, the discussion naturally extended towards virtualisation techniques and performance considerations. Similarly, hydration issues led to conversations around server-side rendering and client-side rendering behaviour in Next.js.</p><p>My suggestion would be to prepare concepts deeply rather than memorising definitions. Most answers will lead to two or three follow-up questions.</p><h3>Redux</h3><p>The Redux discussion focused on understanding both the architecture and practical implementation.</p><p>Questions included:</p><ul><li>Explain Redux architecture and its data flow.</li><li>Which hooks are available with Redux?</li><li>How do you access state values inside components?</li><li>Can we create multiple reducers? If yes, how?</li><li>Can components consume values from different reducers simultaneously?</li><li>What are Redux middle-wares, and which ones have you worked with?</li></ul><p>Expect questions around Redux Toolkit and Redux-Saga as well if you mention using it in your projects.</p><h3>Accessibility (a11y &amp; WCAG)</h3><p>I was pleasantly surprised to see accessibility being discussed in detail. Accessibility is often overlooked during interview preparation, but many organisations are now treating it as an important frontend engineering skill.</p><p>Some of the questions asked were:</p><ul><li>What is accessibility and why is it important?</li><li>How have you implemented accessibility in your applications?</li><li>How do screen readers work?</li><li>Which screen readers have you used?</li><li>What practices do you follow to make components accessible?</li></ul><p>The discussion wasn’t limited to theory. The interviewer was interested in understanding how accessibility considerations influence component design decisions in production applications.</p><p>If you’re preparing for frontend interviews, I’d strongly recommend spending some time understanding:</p><ul><li>Semantic HTML</li><li>Keyboard navigation</li><li>ARIA attributes</li><li>Screen readers</li><li>WCAG guidelines</li><li>Accessible component patterns</li></ul><h3>Performance &amp; Testing</h3><p>Performance optimisation was another major focus area.</p><p>Questions included:</p><ul><li>Why do we use bundlers such as Webpack and Vite?</li><li>What are the advantages of Webpack over Vite and vice versa?</li><li>If your application’s bundle size becomes significantly large, how would you optimise it?</li><li>How does code splitting and chunk splitting work in Webpack?</li><li>What are Core Web Vitals and how would you measure them?</li></ul><p>The testing-related questions included:</p><ul><li>Which library have you used for unit testing in React and why?</li><li>How would you test a button click event using React Testing Library and Jest?</li></ul><p>These questions often lead to discussions around lazy loading, tree shaking, dynamic imports, and improving application performance in production environments.</p><h3>Overall Experience</h3><p>The interview wasn’t designed to test obscure concepts or framework-specific tricks. Instead, it focused heavily on frontend engineering fundamentals and understanding the reasoning behind technical decisions.</p><p>The topics covered included:</p><ul><li>JavaScript fundamentals</li><li>React.js and Next.js</li><li>State management with Redux</li><li>Accessibility and WCAG practices</li><li>Performance optimisation</li><li>Bundlers and code splitting</li><li>Testing strategies</li><li>Problem-solving and coding</li></ul><p>One thing I particularly liked was the number of follow-up questions. The interviewer wasn’t merely checking whether I knew a definition — they wanted to understand how I approach solving real-world problems.</p><p>A simple question like “How would you render a large list?” can easily evolve into discussions around:</p><ul><li>Virtualisation</li><li>Memoisation</li><li>Pagination</li><li>Infinite scrolling</li><li>Performance bottlenecks</li><li>Bundle optimisation</li></ul><p>So, while preparing, try to go one level deeper for every topic you study.</p><h3>Preparation Tips</h3><p>If you’re interviewing for a Senior Frontend role, I would recommend focusing on:</p><ul><li>JavaScript fundamentals and problem-solving.</li><li>React hooks and their execution behaviour.</li><li>Next.js concepts such as hydration, routing, and rendering strategies.</li><li>Redux architecture and middleware.</li><li>Accessibility best practices and WCAG guidelines.</li><li>Performance optimisation techniques.</li><li>Bundlers such as Webpack and Vite.</li><li>Unit testing using Jest and React Testing Library.</li><li>Code splitting and bundle optimisation strategies.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a9acf9f2d53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hackerrank SDE-3 Frontend Interview Experience]]></title>
            <link>https://medium.com/@shashankrai01/hackerrank-sde-3-frontend-interview-experience-ed70d4d081d9?source=rss-a4c35d107f51------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed70d4d081d9</guid>
            <category><![CDATA[frontend-interviews]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[hackerrank]]></category>
            <dc:creator><![CDATA[Shashank Rai]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 04:31:59 GMT</pubDate>
            <atom:updated>2026-07-31T04:31:59.013Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hackerrank SDE-3 Frontend Interview Experience (July 2026)</h3><figure><img alt="Hackerrank Logo" src="https://cdn-images-1.medium.com/max/1024/1*vq9j_I_ip0h_O3eGppPF_g.png" /></figure><p>I recently interviewed for the SDE-3 Frontend role at <strong>HackerRank</strong>. The interview process was quite different from traditional frontend interviews as it focused heavily on debugging existing codebases, accessibility, architectural thinking, and effective use of AI tools rather than writing everything from scratch.</p><p>There were two rounds in my interview process:</p><ul><li>Round 1: AI-Assisted Coding Interview (Online Assessment)</li><li>Round 2: Chakra AI (Virtual Voice-to-Voice AI Interview)</li></ul><h3>Round 1: AI-Assisted Coding Interview</h3><p>The online assessment consisted of two practical frontend tasks built on top of an existing React codebase. The project was a Travel App with a Node.js backend.</p><p>One interesting aspect was the availability of an AI assistant similar to GitHub Copilot. However, unlike traditional code generation tools, it was intentionally restricted. It wouldn’t provide direct solutions but was helpful in understanding the codebase, explaining syntax, discussing possible approaches, and debugging problems.</p><p>The interview was less about building features from scratch and more about:</p><ul><li>Understanding unfamiliar codebases</li><li>Debugging intentionally introduced bugs</li><li>Making incremental architectural changes</li><li>Reusing existing abstractions and utilities</li><li>Applying React best practices</li></ul><p>The biggest challenge? There was no access to the browser console. You couldn’t rely on console.log() for debugging, which forced you to reason through the code and understand the application&#39;s data flow.</p><h3>Task 1: Sorting Feature Debugging</h3><p>The first task was to debug and implement a sorting feature for apartment listings.</p><p>The application supported sorting apartments by:</p><ul><li>Price</li><li>Rating</li><li>Title</li></ul><p>The sorting options were displayed inside a modal that opened when the Sort button was pressed.</p><p>At first glance, the implementation looked almost complete. However, several intentionally introduced bugs were scattered throughout the codebase.</p><p>Some of them included:</p><ul><li>Incorrectly destructured state variables.</li><li>Wrong state updates (for example, storing sort direction in the sort type state).</li><li>Incorrect comparator logic (such as comparing titles while sorting by rating).</li><li>Multiple inconsistencies across handlers and state management.</li></ul><p>Apart from fixing the existing bugs, there were additional requirements:</p><ul><li>Persist the selected sorting option when navigating away and returning to the page.</li><li>Update the UI so that the Sort button was displayed only on the homepage.</li></ul><p>The project already contained a custom useLocalStorage hook that could be reused for state persistence, although candidates were free to implement their own solution.</p><p>Implementing the UI requirement required understanding the existing routing structure and component hierarchy instead of simply conditionally rendering a button somewhere in the codebase.</p><p>This task primarily evaluated:</p><ul><li>React state management</li><li>Debugging skills</li><li>Understanding component architecture</li><li>Reusing existing abstractions</li><li>Navigating unfamiliar codebases efficiently</li></ul><h3>Task 2: Accessibility Features</h3><p>The second task focused on accessibility.</p><p>The requirements were:</p><ul><li>High Contrast Mode, toggled using keyboard shortcut 1</li><li>Keyboard Accessibility Mode, toggled using keyboard shortcut 2</li></ul><p>Interestingly, the project already contained provider and wrapper components responsible for handling accessibility functionality. However, they were only partially implemented.</p><p>The expectation wasn’t to create a completely new solution. Instead, candidates had to:</p><ul><li>Understand the existing architecture</li><li>Integrate the providers correctly</li><li>Complete the missing implementation</li><li>Ensure the keyboard shortcuts worked as expected</li></ul><p>This task evaluated:</p><ul><li>Accessibility fundamentals</li><li>Architectural understanding</li><li>Component composition</li><li>Ability to extend existing implementations</li></ul><h3>My Biggest Learning From Round 1</h3><p>The interview wasn’t particularly difficult from an implementation perspective. The difficult part was debugging intentionally introduced bugs.</p><p>A mistake many candidates make in such interviews is immediately jumping into the code and assuming that most of the existing implementation is correct.</p><p>My suggestion would be:</p><blockquote>Spend the first few minutes understanding how the feature is supposed to work before touching the code.</blockquote><p>Try to understand:</p><ul><li>Where the state lives</li><li>How data flows through the application</li><li>Which handlers are responsible for updates</li><li>Which effects are performing side effects</li><li>How components communicate with each other</li></ul><p>Once you understand the expected behaviour, identifying incorrectly wired logic becomes significantly easier.</p><p>The AI assistant can also be quite useful here. Instead of asking it to write solutions, use it for:</p><ul><li>Understanding the component hierarchy</li><li>Explaining unfamiliar patterns</li><li>Discussing debugging approaches</li><li>Validating assumptions about data flow</li></ul><p>Using AI effectively is also being evaluated during the interview.</p><h3>Round 2: Chakra AI (Voice-to-Voice AI Interview)</h3><p>The second round was conducted by Chakra AI and was a virtual voice-to-voice interview.</p><p>Unlike traditional interviews, this round focused more on architectural discussions and practical engineering decisions.</p><p>Some of the topics covered were:</p><ul><li>Deep discussions around my previous projects</li><li>Designing component libraries and their folder structures</li><li>How it will extensible for multiple teams</li><li>Architectural decisions and design patterns</li><li>Accessibility best practices in frontend applications</li><li>Using AI tools in day-to-day development</li><li>Optimising AI usage during development</li><li>Building guardrails while using AI-generated code</li><li>Practical examples of incorporating AI into engineering workflows</li></ul><p>One interesting aspect was that the questions weren’t superficial. If you mentioned designing a component library, expect follow-up questions around:</p><ul><li>Folder structures</li><li>Scalability considerations</li><li>Reusability patterns</li><li>Accessibility requirements</li><li>State management decisions</li><li>API design for components</li></ul><p>Similarly, discussions around AI usage went beyond asking “Do you use AI?”. The focus was more on:</p><ul><li>How you use AI productively</li><li>Where you draw boundaries while relying on AI</li><li>How you validate AI-generated suggestions</li><li>Improving developer productivity without compromising code quality</li></ul><p>Towards the end, I was also given an opportunity to ask questions about the role and the engineering culture.</p><h3>Final Thoughts</h3><p>Although I got rejected after round 2 because role got closed but overall, I found the interview process quite refreshing.</p><p>It wasn’t focused on solving algorithmic problems or building large features from scratch. Instead, it simulated what frontend engineers actually do every day:</p><ul><li>Understanding large codebases</li><li>Debugging problems</li><li>Extending existing architectures</li><li>Building accessible applications</li><li>Making thoughtful design decisions</li><li>Using AI tools effectively and responsibly</li></ul><p>If you’re preparing for this role, I’d recommend focusing on:</p><ul><li>Debugging React applications without relying heavily on console logs</li><li>React state management patterns</li><li>Accessibility fundamentals</li><li>Component library design</li><li>Architectural thinking</li><li>Effective use of AI-assisted development tools</li><li>Reading and understanding unfamiliar codebases quickly</li></ul><p>Finally, don’t treat the existing code as correct. The bugs are intentional. Spend time understanding the expected behaviour first — the implementation usually becomes much easier once the mental model is clear.</p><p>Good luck with your preparation!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed70d4d081d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YesMadam React Native Interview Experience (2026)]]></title>
            <link>https://medium.com/@shashankrai01/yesmadam-react-native-interview-experience-2026-e708832760d7?source=rss-a4c35d107f51------2</link>
            <guid isPermaLink="false">https://medium.com/p/e708832760d7</guid>
            <category><![CDATA[yes-madam]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-native-interview]]></category>
            <dc:creator><![CDATA[Shashank Rai]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 14:20:41 GMT</pubDate>
            <atom:updated>2026-07-27T14:36:18.265Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*cJUY_itbvv5WUy9W0-25vw.jpeg" /></figure><p>I recently interviewed with YesMadam for a React Native Developer role.<br>I was communicated that there will be 2 technical rounds, 1 virtual &amp; 1 F2F.</p><p>The interview discussion was heavily focused on React Native internals, performance optimisation, state management, native integrations, and production-level mobile application concepts.</p><p>Unlike interviews that focus only on React Native APIs, this round tested both conceptual understanding and real-world experience of building and scaling React Native applications.</p><h3>Topics Covered</h3><h3>React &amp; React Native Fundamentals</h3><p>The interviewer started with some fundamental React concepts:</p><ul><li>useCallback vs useMemo</li><li>Difference between React.memo and useMemo</li><li>Differences between React Native’s Old Architecture and New Architecture</li></ul><p>These questions were followed by discussions around how React Native has evolved and how the New Architecture addresses performance bottlenecks.</p><h3>React Native New Architecture</h3><p>There were several questions around the New Architecture, including:</p><ul><li>What is JSI (JavaScript Interface)?</li><li>What are Turbo Modules?</li><li>Why are Turbo Modules better than Native Modules?</li><li>Benefits of moving away from the traditional bridge architecture.</li></ul><p>A good understanding of how JavaScript communicates with native code is expected.</p><h3>Performance Optimisation</h3><p>A major portion of the interview focused on performance optimisation.</p><p>Questions included:</p><ul><li>How would you optimise rendering a large list of images?</li><li>How do you optimise FlatList performance?</li><li>What is getItemLayout and when should it be used?</li><li>How do you profile React Native components?</li><li>Can we analyse which package is contributing how much size to the final application bundle?</li></ul><p>The interviewer was particularly interested in practical optimisation techniques used in production applications.</p><h3>Reanimated</h3><p>There were questions around React Native Reanimated, including:</p><ul><li>Have you worked with Reanimated?</li><li>What is runOnJS?</li><li>What is runOnUI?</li><li>When should each be used?</li></ul><p>Understanding how animations are executed on the UI thread was an important discussion point.</p><h3>State Management</h3><p>The interviewer covered multiple state management solutions.</p><h4>Zustand</h4><ul><li>Have you worked with Zustand?</li><li>How is Zustand used?</li><li>What are the differences between Zustand and Redux ? And when to prefer zustand over redux ?</li></ul><h4>RTK Query</h4><ul><li>Have you worked with RTK Query?</li><li>What is normalised caching?</li><li>How does normalised caching improve performance and state management?</li></ul><h3>Storage Solutions</h3><p>Questions included:</p><ul><li>Differences between React MMKV and AsyncStorage.</li><li>Which one would you prefer and why?</li></ul><p>The discussion revolved around performance characteristics, synchronous vs asynchronous operations, and appropriate use cases.</p><h3>Analytics, Crash Reporting and Monitoring</h3><p>Production applications require proper monitoring, which was another focus area.</p><p>Questions included:</p><ul><li>Which analytics tools have you used in React Native?</li><li>Can we track which screen caused an application crash?</li><li>Can we identify the exact line responsible for the crash?</li></ul><p>The interviewer also asked about:</p><ul><li>What are source maps?</li><li>How do we generate source maps in React Native?</li></ul><h3>Mobile Integrations</h3><p>Several practical mobile development topics were covered:</p><ul><li>Payment Gateway integration and complete payment flow.</li><li>Overview of setting up Push Notifications in React Native.</li><li>What is Deferred Deep Linking?</li><li>Dynamic App Icons and their implementation.</li></ul><p>These questions were more experience-based and focused on production use cases.</p><h3>OTA Updates</h3><p>Another interesting discussion was around OTA (Over-the-Air) updates.</p><p>Questions included:</p><ul><li>How do OTA updates work in React Native?</li><li>Can native code changes be shipped through OTA updates?</li></ul><p>This topic tests the understanding of limitations associated with OTA updates and what can or cannot be delivered without publishing a new application build.</p><h3>Round 2 — Machine Coding Round</h3><p>The second round was a machine coding exercise where I was asked to build a small e-commerce application using React Native.</p><h3>Requirements</h3><p>The application needed to have the following screens:</p><ul><li>Login Screen</li><li>Signup Screen</li><li>Home Screen</li><li>Cart Screen</li></ul><p>The interviewer asked to implement:</p><ul><li>User authentication flow (Login and Signup).</li><li>Local storage for persisting user authentication and cart data.</li><li>Fetching products either from an API or a local JSON file.</li><li>Displaying the list of products on the Home screen.</li><li>Adding products to the cart.</li><li>Displaying all the added products on the Cart screen.</li><li>Persisting the cart items locally so that they are retained across application restarts.</li></ul><h3>What Was Being Evaluated?</h3><p>This round wasn’t focused on writing a pixel-perfect UI. Instead, the interviewer was interested in evaluating:</p><ul><li>Project structure and folder organisation.</li><li>State management approach.</li><li>Handling local storage efficiently.</li><li>API integration and data flow.</li><li>Navigation between screens.</li><li>Writing scalable and maintainable React Native code.</li><li>Managing authentication and cart states effectively.</li></ul><p>Overall, it was a practical machine coding round that tested the ability to build a small but complete React Native application by combining concepts such as local storage, state management, API handling, and navigation.</p><h3>Final Thoughts</h3><p>This interview was heavily inclined towards senior-level React Native development. It covered:</p><ul><li>React fundamentals</li><li>React Native New Architecture</li><li>Performance optimisation</li><li>State management</li><li>Native integrations</li><li>Analytics and crash monitoring</li><li>OTA updates</li><li>Production-level mobile development concepts</li><li>Machine coding involving authentication, local storage, and cart management</li></ul><p>If you’re preparing for a React Native role, I would strongly recommend focusing not only on React Native APIs but also on topics such as FlatList optimisation, JSI, Turbo Modules, source maps, OTA updates, state management libraries, analytics tools, and application performance profiling.</p><p>I hope this interview experience helps you prepare better for their upcoming React Native interviews.</p><p>Happy learning and all the best for your interviews!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e708832760d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Does an App Remember Where to Navigate After Installation?]]></title>
            <link>https://medium.com/@shashankrai01/how-does-an-app-remember-where-to-navigate-after-installation-c4ac00a91fe0?source=rss-a4c35d107f51------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4ac00a91fe0</guid>
            <category><![CDATA[deep-linking]]></category>
            <category><![CDATA[contextual-deeplinking]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Shashank Rai]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 07:57:28 GMT</pubDate>
            <atom:updated>2026-07-27T07:57:28.759Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Does an App Remember Where to Navigate After Installation? — Understanding Deferred Deep Linking</h3><p>Imagine this.</p><p>You’re browsing Amazon and your friend sends you a link to a pair of headphones. You click on it, but you don’t have the Amazon app installed.</p><p>You’re redirected to the Play Store. You install the application and open it for the very first time.</p><p>Surprisingly, you’re not taken to the home screen. You’re looking at the exact product your friend shared just a few moments ago.</p><p>No searching, No extra clicks, No “Continue” button.</p><p>Just a seamless experience.</p><p>Have you ever wondered how the application knew where to navigate?</p><p>More importantly, where did the original link go during the installation process?</p><p>That’s the question that led me to explore Deferred Deep Linking.</p><p>Let’s start with normal Deep Linking.</p><p>Things are pretty straightforward when the application is already installed.</p><blockquote><strong><em>Click Link → Open App → Receive URL → Navigate</em></strong></blockquote><p><em>React Native makes this extremely simple using the Linking API.</em></p><p>Now let’s assume</p><blockquote><strong><em>Click Link → App isn’t installed → Redirected to Play/App Store → Install App → Open App → ??? → Navigate</em></strong></blockquote><p>Did you notice the problem?</p><p>Somewhere between leaving our browser and opening the application, we’ve lost the original context. The moment users are redirected to the Play Store or App Store, they’ve effectively left our application’s ecosystem.</p><p>At this point, several questions arise:</p><ul><li>Which product did they click?</li><li>Which campaign brought them here?</li><li>How do we preserve that information during installation?</li><li>How do we identify the same user after installation?</li><li>How does the application retrieve that information on its first launch?</li></ul><p>Deferred Deep Linking exists to solve exactly these problems.</p><p>Deep Linking = Navigation</p><p>Deferred Deep Linking = Navigation + Attribution + Context Preservation</p><figure><img alt="DeepLinking Diagram" src="https://cdn-images-1.medium.com/max/1024/1*xr8PeJiT-W1fx8w0XuJpIw.png" /></figure><blockquote>Preserving a user’s intent throughout the installation lifecycle is where things become interesting.</blockquote><p>Let’s follow what actually happens behind the scenes.</p><figure><img alt="Deferred Deepling user flow" src="https://cdn-images-1.medium.com/max/823/1*wk3DHwWnReVWcA7yRt4rYQ.png" /><figcaption>User Flow</figcaption></figure><h3>Step 1: User Clicks a Link</h3><p>Suppose a user clicks:</p><pre>https://example.com/product/123</pre><p>At this point, the user could have arrived from:</p><ul><li>Social media</li><li>Marketing campaigns</li><li>Email links</li><li>Referral programmes</li><li>Advertisements</li><li>QR codes</li></ul><p>The link itself contains valuable information that we don’t want to lose.</p><p>For example:</p><pre>Product ID<br>Campaign ID<br>Referral Code<br>Medium<br>Timestamp<br>Source</pre><p>This information becomes extremely important later in the flow.</p><h3>Step 2: Preserving Context</h3><p>Before redirecting users to the App Store or Play Store, the system preserves the necessary context.</p><p>For example:</p><pre>{<br>    productId: 123,<br>    campaign: &quot;summer-sale&quot;,<br>    medium: &quot;social&quot;,<br>    referralCode: &quot;ABC123&quot;<br>}</pre><p>This information can be:</p><ul><li>Stored by attribution services</li><li>Preserved using backend systems</li><li>Associated with tokens or identifiers</li><li>Retrieved later during application launch</li></ul><p>At this point, the system’s responsibility changes.</p><p>Instead of asking:</p><blockquote><em>Where should users navigate?</em></blockquote><p>We’re now asking:</p><blockquote><em>How do we remember what users intended to do?</em></blockquote><h3>Step 3: The Journey Through Installation</h3><p>The user is now redirected to:</p><pre>Play Store<br>   OR<br> App Store</pre><p>The application is installed and launched for the very first time.</p><p>This creates another interesting challenge.</p><pre>Browser<br>   ↓<br>Play Store<br>   ↓<br>Installation<br>   ↓<br>Application Launch</pre><p>Notice something?</p><p>There is no direct communication happening between:</p><ul><li>The original browser session</li><li>The App Store</li><li>The application’s first launch</li></ul><p>Some mechanism must bridge this gap.</p><p>This is where attribution systems become extremely important.</p><h3>What Happens Behind The Scenes?</h3><p>There isn’t a single implementation for Deferred Deep Linking.</p><p>Different mechanisms can work together depending upon the application’s requirements.</p><p>Some commonly used approaches include:</p><h3>Android</h3><ul><li>Install Referrer API</li><li>Android App Links</li><li>Attribution SDKs</li></ul><h3>iOS</h3><ul><li>Universal Links</li><li>Attribution APIs</li><li>Native SDK integrations</li></ul><h3>Backend Services</h3><ul><li>Token mapping</li><li>Context preservation</li><li>Campaign tracking</li><li>Analytics services</li></ul><p>The overall flow looks something like this:</p><pre>Store Metadata<br>      ↓<br>Install Application<br>      ↓<br>Retrieve Attribution Data<br>      ↓<br>Initialize SDK<br>      ↓<br>Receive Deep Link Parameters<br>      ↓<br>Navigate</pre><p>Regardless of the implementation, the objective remains the same:</p><blockquote><em>Preserve the user’s original intent.</em></blockquote><h3>How React Native Fits Into The Picture</h3><p>One common misconception is that React Native implements Deferred Deep Linking.</p><p>It doesn’t.</p><p>React Native’s responsibility begins only after the pending information becomes available.</p><p>A simplified flow looks like this:</p><pre>Native Layer<br>      ↓<br>Retrieves Deep Link Data<br>      ↓<br> React Native Bridge<br>      ↓<br> Javascript Thread<br>      ↓<br>Navigation Layer<br>      ↓<br> Navigate to Screen</pre><p>Once the native layer retrieves the required information, it can pass the parameters to the JavaScript layer, allowing the navigation system to redirect users appropriately.</p><p>For example:</p><ul><li>Product Screen</li><li>Referral Screen</li><li>Offer Screen</li><li>Profile Screen</li><li>Promotional Campaigns</li></ul><p>React Native isn’t preserving the user’s intent.</p><p>It’s simply consuming the information once it becomes available.</p><p>Understanding this distinction makes it much easier to reason about Deferred Deep Linking during system design discussions.</p><h3>Production Considerations</h3><p>Real-world applications introduce additional complexities.</p><p>Some questions worth thinking about are:</p><ul><li>What if users aren’t authenticated?</li><li>What if SDK initialisation fails?</li><li>What if users kill the application during navigation?</li><li>What happens when campaigns expire?</li><li>Should pending links be preserved after login?</li><li>How should analytics events be tracked?</li></ul><p>Consider the following scenario.</p><pre>User opens application<br>          ↓<br> Deferred link retrieved<br>          ↓<br> Is user authenticated?<br>        /      \<br>      No       Yes<br>      ↓         ↓<br> Navigate     Product Page<br>  to Login<br>      ↓<br>Successful Login<br>      ↓<br>Retrieve Pending Link<br>      ↓<br>Navigate</pre><p>In many production systems, pending links are temporarily stored until authentication is completed.</p><p>Only after successful authentication do we perform the final navigation.</p><p>This significantly improves the overall user experience.</p><p>Similarly, systems should also consider:</p><ul><li>Offline scenarios</li><li>Multiple pending links</li><li>Failed attribution requests</li><li>Application updates</li><li>Analytics and campaign tracking</li></ul><p>These considerations are often what differentiate production-ready implementations from simple demonstrations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4ac00a91fe0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>