<?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 Ritik Varshney on Medium]]></title>
        <description><![CDATA[Stories by Ritik Varshney on Medium]]></description>
        <link>https://medium.com/@ritikvarshney2014?source=rss-1850af18460a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2dsm1AOhG-XAJ4tGJZv0fw.jpeg</url>
            <title>Stories by Ritik Varshney on Medium</title>
            <link>https://medium.com/@ritikvarshney2014?source=rss-1850af18460a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:17:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritikvarshney2014/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[Flipkart UI-2 Interview Experience]]></title>
            <link>https://medium.com/@ritikvarshney2014/flipkart-ui-2-interview-experience-24eeaa630e41?source=rss-1850af18460a------2</link>
            <guid isPermaLink="false">https://medium.com/p/24eeaa630e41</guid>
            <category><![CDATA[ui-2]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Ritik Varshney]]></dc:creator>
            <pubDate>Fri, 28 Aug 2026 06:52:25 GMT</pubDate>
            <atom:updated>2026-08-28T06:53:22.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MgAJ0BgNqiE7LCVp05y5Cw.png" /></figure><p>I recently interviewed for the <strong>UI-2 position at Flipkart</strong>. The interview process covered DSA, frontend machine coding, frontend fundamentals, and system design.</p><p>Here’s a breakdown of the rounds and what was discussed.</p><h3>Round 1 — HackerEarth: DSA</h3><p>The first round was an online <strong>HackerEarth coding assessment</strong> consisting of <strong>2 DSA problems</strong>.</p><p>The focus was primarily on problem-solving ability, understanding the constraints, and writing an efficient solution within the given time.</p><p><strong>Preparation areas:</strong></p><ul><li>Arrays &amp; Strings</li><li>Hashing</li><li>Two Pointers / Sliding Window</li><li>Sorting</li><li>Time &amp; Space Complexity</li><li>Common DSA patterns</li></ul><h3>Round 2 — Frontend Machine Coding</h3><p>The second round was a <strong>frontend machine coding challenge</strong> focused on building a <strong>Creative Management Dashboard</strong> using React.</p><p>The application allowed users to create and manage “Creatives”, where each creative consisted of:</p><ul><li>Title</li><li>Subtitle</li><li>Background color</li></ul><p>The background colors had to be fetched dynamically from an API.</p><p>This round was a good test of how well you can translate a <strong>design specification into a production-quality frontend implementation</strong>.</p><h3>Round 3 — Machine Coding Evaluation + Frontend Tech</h3><p>The third round focused on discussing the machine coding solution and evaluating the engineering decisions behind it.</p><p>The discussion covered areas such as:</p><ul><li>Why the component structure was designed the way it was</li><li>State management decisions</li><li>Handling API data</li><li>Filtering implementation</li><li>Component reusability</li><li>Performance optimizations</li><li>Edge cases</li><li>React fundamentals</li><li>Frontend architecture and best practices</li></ul><p>This round was less about writing new code and more about <strong>defending the design and implementation choices</strong> made during the machine coding round.</p><h3>Round 4 — System Design</h3><p>This round focused on <strong>Frontend/System Design</strong>.</p><h3>Problem: Design a Real-Time Collaborative Map</h3><p>The problem was to design a collaborative map application where <strong>multiple users can edit the map simultaneously</strong>, similar to the collaborative experience of Google Docs.</p><p>Multiple users should be able to view and modify the same map in real time.</p><p><strong>Functional Requirements</strong></p><p>The system should allow users to:</p><ul><li>View the map</li><li>Add markers</li><li>Move markers</li><li>Delete markers</li><li>See changes made by other users in real time</li><li>Allow multiple users to edit simultaneously</li><li>Handle conflicts when multiple users modify the same marker</li></ul><p>The round was primarily about thinking through the <strong>architecture, data flow, real-time synchronization, and conflict-resolution strategy</strong>, rather than simply drawing boxes on a system-design diagram.</p><p><strong>Outcome —</strong></p><p>Although the overall experience was very positive and I learned a lot through the process, I unfortunately did not qualify for the final round (Hiring Manager).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24eeaa630e41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Atlassian Senior Frontend Engineer — P40 Interview Experience]]></title>
            <link>https://medium.com/@ritikvarshney2014/atlassian-senior-frontend-engineer-p40-interview-experience-708ec7f47329?source=rss-1850af18460a------2</link>
            <guid isPermaLink="false">https://medium.com/p/708ec7f47329</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Ritik Varshney]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 05:54:32 GMT</pubDate>
            <atom:updated>2026-02-23T05:55:33.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jde6OhHDao3qdFW1Z-ra-w.png" /></figure><p>I recently went through the interview process for the <strong>Senior Frontend Engineer (P40)</strong> role at Atlassian, and wanted to share my experience. Overall, the process was well-structured and deeply focused on JavaScript fundamentals, browser knowledge, and frontend system design.</p><p>Overall, the experience was great — very structured, technically deep, and product-focused. The entire process, however, took close to <strong>1.5 months</strong>, which required patience and consistency.</p><h3>Round 1 — Karat Round</h3><p>This was an initial screening round taken by third party</p><h3>Introduction</h3><ul><li>Background discussion</li><li>Past projects</li></ul><h3>JavaScript Output-Based Questions</h3><p>Very strong focus on JS fundamentals:</p><ul><li>Hoisting</li><li>Object behavior &amp; references</li><li>Rest &amp; Spread operators</li><li>Promise chaining</li><li>Immutability in JavaScript</li></ul><h3>Coding Questions (Vanilla JS)</h3><ul><li>Implement pagination:<br>- Fetch 5 entries on each button click<br>- Manage state correctly</li><li>Add / Remove items dynamically from a list</li><li>They expected clean logic and edge-case handling.</li></ul><h3>Round 2 — JavaScript Coding Round</h3><p>This round was deeper into problem-solving and patterns.</p><p>Topics covered:</p><ul><li>API retry mechanism (with exponential backoff)</li><li>Promise chaining &amp; error handling</li><li>Implementing a custom Event Emitter</li><li>Circuit Breaker pattern</li><li>Designing a lightweight Analytics SDK (variation-based problem)</li></ul><h3>Round 3 — Browser Coding Round</h3><p>This was a UI-heavy round.</p><h3>Problem:</h3><p>Build a playlist rendering UI.</p><p>Focus areas:</p><ul><li>Efficient rendering</li><li>Handling error scenarios</li><li>Proper state management</li><li>CSS layout &amp; responsiveness</li></ul><h3>Round 4 — System Design (Frontend-Focused)</h3><h3><strong>Design: Cookie Consent &amp; Preferences Feature</strong></h3><p>This was a very interesting round.</p><p>Discussion included:</p><ul><li>Functional &amp; non-functional requirements</li><li>Building it as a reusable library</li><li>Cookie data model design</li><li>What cookies are (technical depth)</li><li>Essential vs Non-essential cookies</li><li>Persistence strategy</li><li>How to integrate across multiple apps</li></ul><h3>Outcome -</h3><p>Although the overall experience was very positive and I learned a lot through the process, I unfortunately did not qualify for the next two rounds (Managerial and Values round).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=708ec7f47329" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frontend Engineer Interview Experience — MakeMyTrip (SSE-2)]]></title>
            <link>https://medium.com/@ritikvarshney2014/frontend-engineer-interview-experience-makemytrip-sse-2-15a3f7653706?source=rss-1850af18460a------2</link>
            <guid isPermaLink="false">https://medium.com/p/15a3f7653706</guid>
            <dc:creator><![CDATA[Ritik Varshney]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 07:59:48 GMT</pubDate>
            <atom:updated>2026-01-19T07:59:48.442Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Frontend Engineer Interview Experience — MakeMyTrip (SSE-2)</strong></h3><p>I recently went through a multi-round frontend engineering interview process. Below is a detailed breakdown of each round, along with the topics covered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*YxM45iwHVHIqlBewemS32A.png" /></figure><p><strong>Round 1 — JavaScript Fundamentals &amp; Coding</strong></p><p>This round focused heavily on core JavaScript concepts and problem-solving:</p><p><strong>Topics Discussed:</strong></p><ul><li>JavaScript fundamentals</li><li>Closures</li><li>Hoisting</li><li>Differences between let and var</li><li>Scope and execution context</li><li>Debouncing vs Throttling</li><li>Output-based questions on setTimeout</li><li>Debugging strategies for frontend applications</li><li>How to identify and fix production issues</li></ul><p><strong>Coding Problem:</strong></p><ul><li><em>Valid Parentheses</em> (LeetCode) — focused on logic, code quality, and edge cases</li></ul><p><strong>Round 2 — Frontend Architecture &amp; Deep Concepts</strong></p><p>This round went deeper into real-world frontend design and performance topics.</p><p><strong>Discussion Points:</strong></p><ul><li>My role and responsibilities at Lowe’s</li><li>CSR vs SSR — explained in depth</li><li>SEO optimization strategies</li><li>How a webpage renders in the browser (critical rendering path)</li><li><strong>Architecture &amp; System Design Topics:</strong></li><li>When to use CSR vs SSR</li><li>Typical architecture flow:</li><li>CDN → Caching → Server → Render Pages</li><li>How browsers determine cache hit vs miss</li><li>Network-level caching behavior</li></ul><p><strong>Hands-on Concepts:</strong></p><ul><li>Debouncing implementation and use cases</li><li>Redux middleware / Redux Saga /Redux Thunks</li></ul><p><strong>Round 3 — System Design &amp; High-Level Design (HLD)</strong></p><p>This round focused on design thinking and architecture skills.</p><p><strong>What Was Covered:</strong></p><ul><li>Personal introduction</li><li>Detailed explanation of one major project</li><li>Architecture diagrams</li><li>High-level design explanation</li><li>Trade-offs and design decisions</li><li><strong>Design Problem:</strong></li><li>Design of a filter and Sorting feature</li><li>Data flow</li><li>API design</li><li>State management</li><li>Performance considerations</li></ul><p><strong>Round 4 — Advanced Frontend Concepts</strong></p><p>This was the most in-depth and experience-driven round.</p><p><strong>Topics I Was Grilled On:</strong></p><ul><li>Akamai EdgeWorkers</li><li>IntersectionObserver API</li><li>Core Web Vitals</li><li>Frontend performance optimizations</li><li>Difference between: dns-prefetch vs preconnect</li></ul><p><strong>Overall Experience</strong></p><p>The interview process was very well-rounded and covered:</p><ul><li>Core JavaScript knowledge</li><li>Practical frontend debugging</li><li>System design</li><li>Architecture decisions</li><li>Performance engineering</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a3f7653706" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>