Compiled from 2024-2026 candidate reports on Glassdoor, Reddit, and community forums.
Q1Swiggy - LLD
Design a delivery assignment system that matches orders to nearby riders in under 2 seconds.
Tip: Start with a simple geospatial index (geohash or quadtree). Talk about rider state (online/busy/offline), load balancing across riders, and what happens when a rider declines. For senior roles, extend to multi-order batching. Draw a diagram, state your assumptions, and iterate.
Q2Zomato - Machine Coding
Build a restaurant search component with filters (cuisine, rating, price) using React. 90 minutes.
Tip: Focus on working code first, polish later. Use a single state object or useReducer for filters. Debounce the search input. Handle loading and empty states. Interviewers watch how you structure components, not whether you finish every feature.
Q3Flipkart - DSA
Given a list of products and categories, find the top K most-viewed products per category in the last hour.
Tip: A heap per category is the textbook answer. For a streaming variant, mention approximate algorithms (count-min sketch). Discuss memory trade-offs and what happens at Flipkart scale (millions of products). Always ask clarifying questions before coding.
Q4Swiggy - DSA
Given a graph of restaurants and delivery zones, find the shortest path a rider can take to deliver 3 orders optimally.
Tip: This is a Travelling Salesman variant. For small K (<=10), DP with bitmask works. For real-world scale, mention greedy heuristics + 2-opt. Interviewer cares more about how you reason about constraints than whether you code TSP perfectly.
Q5Zomato - JavaScript
Explain how the JavaScript event loop handles this: setTimeout(() => console.log('a'), 0); Promise.resolve().then(() => console.log('b')); console.log('c');
Tip: Output is c b a. Explain the call stack, microtask queue (Promises), and macrotask queue (setTimeout). Microtasks run before the next macrotask. Zomato loves this question because it reveals how deep your JS knowledge actually goes.
Q6Flipkart - HLD
Design Flipkart's flash sale system that handles 10 million users clicking buy at 12:00:00 PM.
Tip: Key concepts: queueing (users enter a virtual waiting room), distributed locks on inventory, eventual consistency for cart updates, graceful degradation. Mention CDN for static pages, Redis for counters, and idempotency keys. Show you understand the difference between "available to view" and "available to buy."
Q7Swiggy - Behavioral
Tell me about a time you shipped something to production and it broke. What did you do?
Tip: Use STAR (Situation, Task, Action, Result). Pick a real example where you were accountable. Swiggy values engineers who own their bugs — don't blame teammates or vague "the API was slow" excuses. End with what you changed in your process.
Q8Zomato - React
What is React reconciliation and how does the virtual DOM diff work?
Tip: Explain the tree diffing algorithm, why React uses keys (to track element identity across re-renders), and when Fiber was introduced (React 16) to enable incremental rendering. Bonus: mention useMemo/useCallback and when they actually help vs. hurt performance.
Q9Flipkart - DSA
Given an e-commerce cart, write code to find the minimum number of discount coupons to achieve a target discount amount.
Tip: This is the classic "coin change" DP problem. State: dp[amount] = min coupons needed. Transition: dp[i] = min(dp[i], dp[i - coupon] + 1). Handle the "impossible" case. Flipkart often frames DSA as shopping problems — the structure is still classic DP.
Q10Swiggy - LLD
Design the rate-limiting layer for Swiggy's public API. Handle burst traffic during lunch hour.
Tip: Token bucket or leaky bucket. Discuss trade-offs (token bucket allows bursts, leaky smooths). Mention where rate limiting lives (gateway vs. service), how to handle distributed state (Redis), and what headers to return (X-RateLimit-Remaining). Bonus: adaptive limits based on user tier.
Q11Zomato - Product
You are a PM at Zomato. Dineout bookings dropped 15% this week. How do you investigate?
Tip: Break it down. Ask: which cities, which time slots, which restaurant tiers? Check recent app releases or A/B tests. Look at funnel metrics — is it fewer searches, fewer views, or fewer conversions? Don't propose solutions until you have hypotheses backed by data. PMs are graded on structured thinking, not jumping to fixes.
Q12Flipkart - Culture
Why Flipkart over Amazon or Meesho? What do you know about our customer base?
Tip: Show you've done homework. Flipkart's strength is tier-2/tier-3 India penetration, vernacular experience, and Big Billion Days scale. Mention a specific Flipkart product or initiative (PhonePe, Myntra, Shopsy) and connect it to why you want to join. Generic "I like your company" fails.
Q13Swiggy - SQL
Write a SQL query to find the top 3 restaurants in each city by monthly order volume.
Tip: Use ROW_NUMBER() OVER (PARTITION BY city ORDER BY order_count DESC), then filter where rank <= 3. Interviewer may follow up with "what if two restaurants tie?" — then use DENSE_RANK(). Swiggy data roles test SQL thoroughly, especially window functions.
Q14Zomato - CSS
Build a responsive restaurant card that works from 320px mobile up to 1920px desktop without media queries.
Tip: CSS Grid with repeat(auto-fit, minmax(240px, 1fr)) or clamp() for fluid typography. Container queries (@container) are now widely supported in 2026 and Zomato loves candidates who know them. Demo fluid spacing, aspect-ratio, and accessible focus states.
Q15Flipkart - HM Round
What's the most impactful project you've shipped? Walk me through the scope, your decisions, and the outcome.
Tip: Quantify impact (users affected, latency reduction, revenue moved). Own the trade-offs you made. Be honest about what you'd do differently. Flipkart hiring managers use this to assess ownership and seniority. Practice this 3-4 times before the real interview — it's the most common "make or break" question.