← Interview experiences
Rejected

Software Development Engineer II at Flipkart

Difficulty
Process took
2-3 Weeks
Rounds
4
Format
Remote
Applied via
Referral

How it went

  • Even after clearing all rounds, not getting an offer can be tough, but it can also be revealing.
  • For me, this was a wake-up call on the difference between theoretical knowledge and production-grade system design.
  • If you're preparing for Flipkart or any top product company, I’d strongly recommend doubling down on: 1. Machine coding round-style problems 2. Infra design thinking 3. Handling real-world constraints

What they would tell you

  • Even after clearing all rounds, not getting an offer can be tough, but it can also be revealing.
  • For me, this was a wake-up call on the difference between theoretical knowledge and production-grade system design.
  • If you're preparing for Flipkart or any top product company, I’d strongly recommend doubling down on: 1. Machine coding round-style problems 2. Infra design thinking 3. Handling real-world constraints

How to prepare

  • I have 2–3 strong project stories that reflect ownership, delivery under constraints, and learning mindset.
  • Stick to core topics like graphs, trees, arrays, heaps.

Round by round

  1. 1

    Machine Coding60 min

    I was asked to design and implement a Flight Booking System. The focus was on writing production-quality code with a clean, extensible architecture. I had to ensure proper class design, a modular structure, and clear separation of concerns throughout the solution. This was one of the most realistic and insightful rounds. It wasn’t just about solving the problem, it really tested my ability to write maintainable and testable code.

  2. 2

    Data Structures & Algorithms60 min

    I had a technical round where the emphasis wasn’t just on solving the problems but also on how I approached them and communicated my thought process throughout. The first question was Gas Station, a classic problem involving circular arrays and greedy logic. I walked through the brute-force approach first, then quickly moved to the optimized greedy method. The second was Sum of Subarray Minimums, which required a solid grasp of monotonic stacks. I initially thought of using a brute-force nested loop but quickly pivoted to the stack-based approach to keep the time complexity under control.

  3. 3

    System Design60 min

    I was asked to design a trading platform like Zerodha, and the conversation quickly turned into a deep dive on how real systems are built at scale. We talked about how I did break the system into services, make it scalable, and keep it fault-tolerant. There was a good discussion around tech choices, and I was asked to explain the trade-offs behind them.

  4. 4

    Hiring Manager45 min

    This round was a mix of deep-diving into past projects and behavioral questions. I spoke about a key project where I had end-to-end ownership, from design to delivery. We discussed the architecture, the data model, and the tech stack choices, including the trade-offs I had to make along the way. The conversation also touched on how I worked with my team, especially when facing tight deadlines and constraints, and how we managed to deliver effectively despite the challenges.

What came up

MediumRemote3 4 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources