Candidates describe a Flipkart Software Engineer loop built around a machine-coding round with a walkthrough, DSA, design and a hiring-manager conversation, sometimes preceded by an online assessment. Round counts vary by report.
$33K
Avg. Base Comp
$45K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Flipkart's Software Engineer interview is not a pure LeetCode screen. Many candidates describe a machine-coding round followed by a walkthrough of your own code, and that is the part that stands out most. Reported prompts include a task scheduler that assigns tasks to worker threads and queues them when all workers are busy, and a gym booking app with assign, approve and cancel flows. One candidate said incomplete functionality could end the process early. Others were asked to explain functionality and justify design choices, including how they would decouple the code, so clean structure and clear explanation matter as much as a working result.
DSA appears in nearly every report. One online assessment is described as three coding questions in roughly 60 to 90 minutes. One question was easy-to-medium and two were medium-to-hard, all on arrays and strings, with sliding window and two pointers especially relevant. Reported interview topics include graphs, dynamic programming, trees, binary search, topological sort and a rate-limiter API. Interview rounds are usually described as medium difficulty, though one candidate found the DSA round the hardest technical stage. Interviewers may offer hints, so explain your thinking as you go.
Design rounds vary. Reports mention LLD prompts such as an IRCTC-like system or an airport system, and a vague HLD prompt such as YouTube Shorts where you define the requirements yourself. One candidate had a combined LLD and HLD round, while another describes a deep architectural discussion of past projects. A frontend-leaning report adds the JavaScript event loop, promises and closures. A hiring-manager round usually comes last, though one candidate says late rounds can still turn technical.
Outcomes were mixed across the reports, and round counts ranged from two to five, so the loop is not identical for every candidate. Prepare for the stages, not a fixed script.
Synthesized from 33 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Flipkart process.
My experience interviewing at Flipkart was somewhat frustrating, though it started with promise. I was contacted by HR and scheduled for an interview. The first technical round went okay. I got questions on graphs and dynamic programming, and there was a general DSA discussion that felt conversational. The interviewer seemed approachable, and I thought I'd done enough to move forward. However, I didn't make it to the system design round. In retrospect, the first round was probably the make-or-break moment, and I must have missed something the interviewer was looking for. What was most disappointing was the lack of clear communication and structured process. Feedback was minimal or non-existent, and the company doesn't seem to have a streamlined hiring pipeline, which made the experience feel disjointed and sometimes dismissive.
Prep tip from this candidate
Graph and DP problems are core to their DSA round—practice those topics rigorously. However, manage expectations: some candidates reported a lack of feedback regardless of performance, so don't treat silence as a sign you should have done more; sometimes it's a process issue on their end.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Flipkart
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| The Brackets Problem | |
| Max Quantity | |
| Dijkstra implementation | |
| Underpricing Algorithm | |
| Hurdles In Data Projects | |
| Biased Random Number Generator | |
| Count Transactions | |
| Receipt Scoring Microservices | |
| Walking Robot | |
| Seller Type Modeling | |
| Text Editor With OOP | |
| Why Do You Want to Work With Us | |
| LRU Cache 1 | |
| Bag of Different Coins | |
| Meta in an Emerging Market | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Top 3 Users | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Scrambled Tickets | |
| Merge Sorted Lists | |
| Customer Orders | |
| Monthly Customer Report | |
| Longest Streak Users | |
| Rolling Bank Transactions | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
One candidate applied through Unstop and took a HackerRank online assessment with three coding questions in about 60 to 90 minutes. One question was easy-to-medium and two felt medium-to-hard. All focused on arrays and strings, with sliding-window and two-pointer techniques. Read long narrative prompts and output instructions carefully. Not every report starts with an assessment.
Candidates report a timed machine-coding round lasting from about 60 minutes to about 2.5 hours, depending on the report. Prompts include a task scheduler that assigns work to worker threads and queues tasks, and a gym booking app with assign, approve and cancel flows. One round was proctored over Google Meet. A working, well-structured implementation is typically expected.
Several candidates describe a separate session of roughly 30 minutes, sometimes the next day, where the machine-coding solution is reviewed. Interviewers ask you to explain functionality, justify design choices and discuss how you would decouple the code. Expect to defend your decisions rather than only demonstrate that the code runs.
Candidates report a DSA round, typically with two medium-level problems. Reported topics include graphs, dynamic programming, trees, topological sort, a rate-limiter API, binary search and sliding window. Interviewers may offer hints, and time-complexity analysis can come up, so explain your approach as you go.
Some candidates report an LLD or combined LLD and HLD round, with prompts such as an IRCTC-like system, an airport system or YouTube Shorts. Others describe an architectural conversation based on their own projects. Because prompts differ by report, prepare to model a real system and state your own requirements. A frontend-oriented candidate was also asked about JavaScript internals.
Candidates typically describe a final hiring-manager conversation. One candidate reports it was largely a discussion of how they use AI day to day, and another says a late round became technical. Have concrete examples from your experience ready.
