Swiggy - Associate Software Development Engineer

This was a hands on React machine coding round. I was asked to build a grid based UI where certain cells were disabled and others could be toggled on user interaction. The interviewer focused on how well I managed component state, handled disabled conditions, and structured reusable components. Special attention was given to clean code, separation of concerns, and performance. I was expected to explain my thought process while coding and justify the approach I took. The round tested real world React development skills rather than theoretical knowledge.

This round focused deeply on JavaScript fundamentals. I was asked questions on closures, promises, async await, and the JavaScript event loop. There were multiple output based questions to test conceptual clarity. React related questions included how rendering works, how to optimize components, and how to prevent unnecessary re renders. The interviewer also asked basic questions about CI/CD pipelines and deployment processes to assess general engineering awareness.

This round was more discussion driven and scenario based. JavaScript concepts like async await, promises, closures, and output based problems were discussed in detail. I was given a scenario where I had to design an approach for fetching employee details and their reportees in a React Native application. I was not required to implement the solution but had to explain the approach clearly. The discussion focused on handling API failures gracefully, optimizing multiple API requests using Promise.all and batching, and improving performance through caching, memoization, pagination, and request prioritization.

This round involved a deep dive into my previous internship and my personal projects. I was asked to explain the complete architecture, technical stack, and reasoning behind design choices. The interviewer tested my ability to explain trade offs, scalability concerns, and edge cases. I was also asked to implement a Pub Sub pattern in JavaScript, followed by questions on improving the design, handling edge cases, and making the solution scalable. Behavioural questions were asked to understand problem solving mindset, ownership, and learning attitude.

The final round focused on problem solving using JavaScript. I was asked to solve three medium level DSA problems. The problems involved array manipulation, implementing async retry logic using promises, and detecting repeating patterns in data. The interviewer evaluated code quality, correctness, and the ability to analyze time and space complexity. Clear explanation of the approach was as important as writing the code.