Interview Experience

The entire process took about 8 weeks from the initial recruiter call to the final offer rollout. The interview loop consisted of three main rounds evaluating core problem-solving, design capability, and engineering experience.

Round 1: External Bar Raiser (60 Mins)

• The Format: This round was conducted by an external bar raiser and focused on a mix of Data Structures & Algorithms (DSA) and Low-Level Design (LLD).
• The Experience: The questions asked were very straightforward and easy to navigate. It was primarily a foundational check on basic coding patterns and clean object-oriented code structuring.

Round 2: Low-Level Design / Machine Coding (90 Mins)

• The Task: I was asked to design and write the pseudo-code for an Inventory Management System tailored for a high-scale service like Swiggy / Instamart.
• Focus Areas: The interviewer focused intensely on how the system handles critical edge cases (like multi-user stock depletion, race conditions during peak flash sales, and handling inventory locks). Clean code, modular class separation, and robust handling of real-world constraints were crucial.

Round 3: Hiring Manager & Architecture (60 Mins)

• Past Experience: A deep, technical dive into the architectures I built at my previous companies, specifically focusing on high-throughput distributed systems.
• System Design & DSA: The discussion smoothly transitioned into High-Level Design (HLD) concepts and quick, algorithmic problem-solving strategies.
• The Vibe: The round concluded with a rapid-fire style Q&A testing overall technical breadth, engineering tradeoffs, team alignment, and situational engineering leadership.

My Preparation Strategy & Advice

• Master Low-Level Design & Concurrency: For companies operating at Swiggy's scale, LLD isn't just about drawing class diagrams. You must practice writing clean, extensible pseudo-code that explicitly accounts for race conditions and data consistency across microservices.
• Know Your Previous Projects Inside Out: Expect hiring managers to dig deeply into your past choices. Be ready to explain why you chose a specific tech stack (like Aerospike, Kafka, or MySQL) and the specific real-world bottlenecks you resolved.
• Focus on DSA Speed and Breadth: Keep your algorithmic problem-solving sharp enough to comfortably handle rapid-fire conceptual questions during structural technical discussions.

Hope this helps the community! Feel free to ask any questions regarding the interview structure or the preparation process below.

Comp: comp link