Flipkart Interview Questions

Candidates commonly report that Flipkart interviews look nothing like an IT services process. Fresher hiring runs largely through campus placements at established engineering institutes, internships converting to pre-placement offers, and engineering contests such as Flipkart GRiD, with an online data structures assessment as the first gate. Laterals, mostly moving from other product companies, typically face a machine coding round, one or two problem solving interviews, a design round scaled to the level being hired for, a hiring manager conversation and an HR discussion. The machine coding round is the part that surprises people: you are given ninety minutes to two hours to build a working, runnable mini application with clean class design, and then defend the design in a follow-up discussion. Reported loops run one to four weeks depending on scheduling, with lateral joining dates set by notice period and any buyout. The common stumble is preparing only competitive programming and neglecting object oriented design under a timer.

The interview process, round by round

1. Online assessment Online, typically 60 to 120 minutes, two to three problems

   Data structures and algorithms on a hosted judge, scored against hidden test cases. Reported difficulty sits at medium to hard by placement standards: arrays and strings, hashing, two pointers, binary search on answer, trees, graphs and dynamic programming. Campus versions commonly attach multiple choice questions on operating systems, DBMS and computer networks. Partial scoring and time to solve both reportedly influence the shortlist.

2. Machine coding round On machine, typically 90 to 120 minutes, one problem

   The round most associated with Flipkart. You build a working command line or in-memory application from a written problem statement, in your own editor and language, with no internet in most reported settings. Evaluation weighs whether it actually runs, class and interface design, separation of concerns, extensibility, edge case handling and readability. Persistence, frameworks and user interfaces are usually explicitly out of scope.

3. Problem solving interview Video call or in person, typically 45 to 60 minutes

   One or two rounds of live coding with an engineer, usually in a shared editor without autocomplete. Candidates commonly report being asked to state the approach and complexity before writing, then to optimise from a brute force, then to handle edge cases and dry run the code. Communication while solving is reported to matter nearly as much as arriving at the optimal solution.

4. Design round Video call or in person, typically 45 to 60 minutes

   Scaled to level. Entry level candidates commonly report a low level design discussion extending their machine coding solution, covering class diagrams, interfaces, design patterns and how a new requirement would be absorbed. More experienced candidates report high level system design on e-commerce shaped problems, covering data modelling, caching, queues, consistency, scale estimation and failure handling.

5. Hiring manager round Video call or in person, typically 30 to 60 minutes

   A senior engineer or engineering manager covers ownership and judgement: a project you drove end to end, a production incident you handled, a technical disagreement and how it resolved, and trade-offs you made under a deadline. Candidates commonly report follow-up technical probing inside this round rather than a purely behavioural conversation, plus questions on why you are moving and what you want next.

6. HR discussion Video call, typically 20 to 30 minutes

   Compensation and logistics. Expect current CTC and its break-up into fixed, variable and stock, expected CTC, competing offers, notice period, buyout possibility and last working day, plus location and onsite expectations for Bengaluru. Candidates commonly report that background verification and document requirements are set out here, including any employment gap that will need explaining.

Interview questions candidates report

Data structures and algorithms

• Given an array, find the length of the longest subarray with a given sum.
• Find the median of two sorted arrays.
• Detect a cycle in a directed graph and return the nodes involved.
• Given a binary tree, return its bottom view.
• Find the minimum number of platforms required for a given train schedule.
• Given a stream of numbers, return the running median efficiently.
• Word ladder: find the shortest transformation sequence between two words.
• Given a matrix of costs, find the minimum cost path with allowed moves.

Machine coding

• Design and build a snake and ladder game supporting multiple players and configurable board size.
• Build a parking lot system with multiple floors, vehicle types and ticketing.
• Implement an expense sharing application supporting equal, exact and percentage splits with balance settlement.
• Build a cricket scoreboard that processes ball by ball input and reports player statistics.
• Implement a movie ticket booking system with seat selection and concurrent booking safety.
• Design an in-memory key value store supporting expiry and simple transactions.
• Build a logistics or delivery slot allocation service given capacity constraints.

System and low level design

• Walk me through the classes in your machine coding solution and why you split them that way.
• How would you extend your design if a new rule or product type were added tomorrow?
• Design a URL shortener and explain how you would handle read heavy traffic.
• Design the order management flow for an e-commerce platform during a sale event.
• How would you design a notification service that must not lose messages?
• Explain how you would keep inventory counts correct under concurrent purchases.
• Which design patterns did you use and what would you have used instead?

Behavioural and hiring manager

• Tell me about a project you owned end to end and the hardest decision in it.
• Describe a production incident you were involved in and what you changed afterwards.
• Tell me about a time you disagreed with a senior engineer or a product manager.
• What is the trade-off you regret making under deadline pressure?
• Why are you looking to move, and why a consumer scale product company?
• What is your notice period, and can it be shortened or bought out?
• How do you decide what to build first when everything is marked urgent?

How to prepare

• Practise machine coding against a stopwatch. Build two or three classic problems such as a parking lot, an expense splitter and a board game from scratch in ninety minutes each, and get used to producing a running programme rather than a perfect one.
• Have a design skeleton you can reach for: entities, services, repositories, interfaces for the parts likely to change, and an in-memory store. Reported evaluation rewards extensibility and clean separation far more than clever algorithms in that round.
• In the coding interviews, state the approach and complexity out loud before typing. Candidates commonly report the interview turning on whether the reasoning was visible, not only on whether the final code compiled.
• Know your own resume in depth. Hiring manager rounds are reported to dig into a single project until they reach something you actually decided, so pick projects where you owned the trade-offs rather than ones that merely sound impressive.
• For laterals, prepare the compensation conversation properly: fixed, variable and stock separated, notice period, buyout position and any competing offer timeline. Reported delays usually come from that conversation, not from the technical rounds.
• For campus candidates, contests such as Flipkart GRiD and internship conversion are widely reported routes in, so treat them as a parallel pipeline rather than as a side activity.

Frequently asked questions

What exactly is the machine coding round?

You are given a written problem statement and typically ninety minutes to two hours to build a working, runnable application in your own editor, usually without internet access. Databases, frameworks and user interfaces are normally out of scope; an in-memory implementation is expected. Evaluation focuses on whether it runs, on class design and extensibility, and on how you defend the design in the discussion that follows.

How does Flipkart hire freshers?

Mainly through campus placements at established engineering institutes, internships that convert to pre-placement offers, and engineering contests such as Flipkart GRiD. Candidates commonly report an online data structures assessment as the first gate, followed by two or three interview rounds. Off-campus fresher hiring is reported to be far less common than at IT services firms.

How much data structures preparation is realistic?

Reported questions sit at medium to hard by placement standards, drawing heavily on arrays, strings, hashing, binary search, trees, graphs and dynamic programming. Most successful candidates describe several months of consistent practice rather than a few weeks of cramming, plus timed mock sessions, since the online round is scored on both correctness and how quickly problems are solved.

What is the notice period and buyout position for laterals?

Most Indian product and services employers set a notice period of one to three months, and candidates commonly report buyout being discussed where the team needs an earlier start. Whether a buyout is supported is reported to vary by role and urgency rather than being guaranteed, so raise it early in the HR discussion rather than after the offer is drafted.

Other Indian employers