Flipkart interview process and practice questions

Behavioral questions

1. Tell me about a time you owned a problem end to end.

   A good answer covers

   • Why it was yours to own, and what would have happened if you hadn't
   • The steps you took yourself, from finding the cause to shipping the fix
   • The result, and what you set up so it stayed fixed

2. Tell me about the boldest bet you've made on a project. What happened?

   A good answer covers

   • What made it bold: the risk, and what the safe option was
   • How you made the case and limited the downside
   • The outcome, including what you learned if it didn't work

3. Describe a time you moved fast to fix something urgent for customers. How did you avoid making it worse?

   A good answer covers

   • Who was affected and why waiting wasn't an option
   • The quick fix and the safety checks around it, such as a flag or a rollback plan
   • The proper fix you made afterwards

4. Tell me about a time you pushed back on a shortcut because it wasn't right for customers or sellers.

   A good answer covers

   • The shortcut, and who it would have hurt
   • How you raised it and what you offered instead
   • What was decided, and how you kept your word on the alternative

5. Tell me about a risk you took that didn't work out. What did you take from it?

   A good answer covers

   • Why the risk seemed worth taking at the time
   • How you found out it wasn't working, and how quickly you stopped or changed course
   • What you'd do the same and what you'd do differently

Role and technical questions

1. Walk me through how you'd design a simple parking-lot or snake-and-ladder system in code.

   A good answer covers

   • The main classes and what each is responsible for, from the requirements
   • A working version first, then how a new rule (vehicle type, board size) fits without rewrites
   • Edge cases and how you'd test them, such as a full lot or a snake at the last square

2. How would you design the cart and checkout flow for a big sale day?

   A good answer covers

   • Clarifying the load: peak orders per second and the few hot products everyone wants
   • Reserving stock at checkout without overselling, and releasing it if payment fails
   • Keeping the rest of the site up: caching, queues, rate limits and graceful fallbacks

3. How would you design a flash sale where a limited stock of a popular phone goes on sale at noon?

   A good answer covers

   • Stock reservation that can't oversell: atomic counters or holds that expire
   • Absorbing the noon spike: a waiting queue, cached product pages and rate limits
   • Fairness and bots, and what shoppers see once stock runs out

4. Explain the SOLID principles with an example from code you've written. Which one do you find hardest to follow?

   A good answer covers

   • Each principle in a sentence, tied to a class you actually wrote
   • How following them made the code easier to extend or test
   • An honest example of where you broke one and why

5. How would you design product search with filters such as brand, price and rating for a very large catalogue?

   A good answer covers

   • A search index with facets for filters, and how it's kept in sync with the catalogue
   • Ranking: relevance, availability, price and popularity
   • Spelling mistakes and mixed-language queries, plus speed and caching

6. Delivery dates shown on product pages are wrong for some pin codes. How would you investigate?

   A good answer covers

   • Narrowing it down: which pin codes, sellers or warehouses, and since when
   • Checking each input: serviceability data, warehouse stock, courier timelines
   • The fix, and a check or alert that would catch it next time

7. How would you improve how many first-time shoppers from smaller towns complete their first order on the app?

   A good answer covers

   • Finding where they drop off in the funnel before proposing fixes
   • Likely barriers: trust, language, payment options such as cash on delivery
   • An experiment, with first-order conversion as the goal and returns as a guardrail

Why Flipkart? Fit and HR questions

1. Why Flipkart? Which of its values do you connect with most, and when have you shown it?

   A good answer covers

   • A reason tied to the team, product or customers, not only the brand
   • One value, named once, with a short example
   • Why that way of working suits you

2. What would you change about the Flipkart app, and how would you know your change worked?

   A good answer covers

   • A specific screen or flow, and the customer problem with it
   • The change you'd make and what you'd leave out
   • The metric that would tell you it worked

Tips

• Practise machine coding: working code first, then clean classes and tests.
• Talk about scale: Big Billion Days traffic is a favourite topic.
• Flipkart's hiring page invites you to ask your recruiter how many rounds to expect; ask what each one covers so you can prepare.
• Flipkart says each interviewer's feedback goes to an independent hiring committee, so give every round your full effort, including the last one.
• Flipkart says it celebrates its biggest risk that didn't work out each year (its Chandrayaan Award), so have an honest failure story ready.
• Its hiring page says you can have only one application under consideration at a time, so choose the role that fits you best.