GeeksforGeeks Question · Jul 2025

Flipkart Interview Experience for SDE2 (2.5 yr Exp.)

Backend Phone Screen

Question Details

Round 1:Machine CodingProblem statement was to design an auction system Foobar where there'll be sellers who can create auction for item they want to sell. They'll be spec...

Full Details

Round 1:Machine Coding Problem statement was to design an auction system Foobar where there'll be sellers who can create auction for item they want to sell. They'll be specifying lowest and highest bid that can be placed and there will be a participation charge applicable on buyers who'll be bidding for this auction. System should be able to handle multiple auctions at a time. Seller's profit/loss will be calculated as : WinningBid + 20% of totalParticipationCostByBuyers - averageOfLowestAndHighestBid. Remaining 80% of participation cost goes to foobar as commission. Winning bid will be highest unique bid . If for a particular auction these are the bids - buyer1 19, buyer2 19, buyer3 17, buyer4 17, buyer5 10 : then buyer5 will be the winner. Following opertaions were required : Create a seller create a buyer auction creation by a registered seller bid on an auction by any registered buyer bid amount can be updated by buyer Withdraw bid close an auction and return the winning bid profit/loss of any seller till now Brownie points for this : If any buyer has placed bid on more than 2 auctions than he is preferred buyer. So if in an auction there are two bids buyer1 19 and buyer2 19 and buyer2 is preferred buyer then he is the winner. If both buyer1 and buyer2 are preferred buyers then fall back to next highest bid and apply the same logic. Expectations : Code should be moduler and all responsibilities shouldn't be jammed in 1/2 classes. Basically they wanted this to be layered : dao layer, api layer like that. Code must be working and demoable. handle failures gracefully Cover corner cases Code must be extensible with minimal changes. So keep in mind the future requirements and use Interfaces and contracts wherever possible. You should be knowing SOLID principles and design patterns for this. Round 2:DS ALGO round https://www.gayle.com/consulting <-- Good one https://www.geeksforgeeks.org/problems/rotten-oranges2536/1 https://www.geeksforgeeks.org/problems/find-median-in-a-stream-1587115620/1 For last 2 questions, interviewer asked to write code on paper. Round 3:System Design Design a system for flipkart for this new idea where flipkart comes up with something like big basket where you cannot purchase things but subscribe to them( For example we subscribe for milk And AppleJuice daily for next 1 month). There will be stores who will be providing these items on flipkart and they'll also be specifying the location where they can deliver. User can subscribe for items - item can come from any store if user is in location range of the store where item is available. Don't worry about the store part and logictics part and focus on subscription model. Your job is to come up with requirements, ask clarifying questions. I talked about microservices on the server side, which all things will your client application handle and how, the database side, payments, what can be made to work asynchronously/synchronously, balancing load on servers, how to handle scale, handle spof, caching, API interfaces, notification to users about discounts, multiple subscription models, which one to choose : SQL vs NoSQL & why, design entities in a manner that it optimizes search queries. He had cross question on everything that I included in my design. He made sure he asked all that he wanted to know, if at all I was going into anything he didn't want in deep, he stopped me and told we don't want to dive that deep into this thing and diverted the discussion to what he wanted to drill on. If there is a point where you are using 1 tech between 2, you should be able to justify on WHY and discuss pros and cons of each. Round 4:Hiring Manager Some of the questions that I remember were : Where do you see yourself in 5 years? If 10-12 years down you career, you plan to become a

manager how would you plan about it from now. How do you plan to approach new team members if you get selected. (I was like whatt !! I will just go and talk to them :P) Where do you rate yourself out of 5 in system design knowledge? What is your weakness? If there is a consumer consuming at at the rate of 10 units per sec. & producer producing at the rate of 100 units per sec, how would you handle this? You cannot use % / * operator, how will you find the value of x/y upto two decimal places? What are you expectation from flipkart and new team if you get selected? Why do you want to work on distributed systems, you have enough sources to learn even though you are not working on them?

Free preview — 6 questions shown. Unlock all Flipkart questions →

About This Question

This is a reported interview question from a flipkart interview for a backend role during the phone screen round reported in 2025.

It covers the following topics: Sql, System Design, Networking, Oop .

About Flipkart Interview Reports

This question was reported by a candidate who interviewed at Flipkart. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Flipkart are the higher-signal extractions to take from this report.

For broader preparation context, the Flipkart interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Flipkart reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Flipkart Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Flipkart reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.