Flipkart machine coding round, and the SDE loop around it.

Updated · Sources at the end

Flipkart's software engineer interview is known for its machine coding round. In it you get a problem statement, such as a conference room booking system or a food ordering app, and about 90 minutes to build a working, runnable program on your own laptop, in a language you choose. Then you demo it, and the interviewer adds a requirement or feeds it bad input to see whether your design holds. Candidates who reach it describe the same checks across a decade of reports: the code runs, edge cases are handled, the classes are modular, and a new rule fits in with a small change. The round comes first for experienced hires and decides whether the rest of the loop happens.

Flipkart is based in Bengaluru and is majority-owned by Walmart. In March 2026 it let go of a few hundred people after its annual performance review, and in May 2026 Walmart reportedly told it to shelve its IPO plans and reach break-even first. It is still hiring senior engineers: it named a VP of Engineering for central platforms in March 2026, and a VP of Fintech and Payments Engineering and a Distinguished Architect in June.

Free · 2 minutes · no account

The questions for your exact Flipkart role and level.

01

Who Flipkart hires

Flipkart hires software development engineers at three levels: SDE-1 (early career), SDE-2 and SDE-3 (senior), plus UI engineers, data scientists and engineers for its quick commerce service, Flipkart Minutes, and its payments app, super.money. In May 2025 it announced 5,000 hires for the year, focused on those two businesses. Most entry-level full-time roles are filled by turning interns into employees, and students reach those internships through campus hiring and GRiD, Flipkart's annual engineering challenge. GRiD 8.0 ran Software Development, AI Engineering and Data Science tracks for graduating classes 2027 to 2030: a 90-minute proctored test, then a case study where you build and ship a working tool for review, then a live hackathon at Flipkart's Bengaluru headquarters for the top 16 in each track.

Not sure your resume shows the level Flipkart hires at? Check it with a free resume review.

Flipkart does not publish its experienced-hire interview. The tracks below come from candidate reports from 2024 to 2026, and they differ mainly after the machine coding round.

  • Track · SDE-1

    Machine coding, problem solving, hiring manager

    About two hours of machine coding, with must-have features first and bonus features if there's time, then a problem solving and data structures round of one or two problems, often written in a shared Google Doc, then a hiring manager conversation of 30 to 45 minutes. Campus and early-career candidates may sit an online test of about three problems first.

  • Track · SDE-2

    Plus a design round

    Machine coding, then problem solving with two LeetCode-medium problems, then a design round, then the hiring manager. Reports from 2025 describe the design round both as high-level design (a ledger system) and as low-level design (a notification system), so prepare both. One candidate was offered a second problem solving round as a second chance.

  • Track · SDE-3

    Concurrency and system design

    The machine coding problem expects thread safety: one December 2024 report says concurrency handling was essential at this level. Then a 60-minute problem solving round, a 90-minute high-level design round (one reported prompt was a quick commerce system), and the hiring manager.

  • Track · UI engineer

    Machine coding in plain JavaScript

    A 2025 UI Engineer 2 report describes a two-hour machine coding round in plain HTML, CSS and JavaScript with a code review, then problem solving with async JavaScript and React reconciliation, a UI technology round, a product sense round and the hiring manager.

02

What is the Flipkart interview process?

These rounds are reported by candidates for SDE-1 to SDE-3 roles in Bengaluru between 2024 and 2026, and they match reports going back to 2015. Experienced hires often start at the machine coding round with no online test. Some drives run all rounds in one day at the office; others spread them over a week or two.

01
Online assessment
About 3 problems in 60 to 90 minutes, on HackerRank

Data structures and algorithms at medium to hard level. Reported for campus and early-career hiring; experienced hires usually skip it.

Campus and early career
02
Machine coding
About 15 to 30 minutes of requirements, 90 minutes of coding, then a demo or review

Build a working console program on your own laptop, in any language. Must-have features first, then extras. The interviewer adds a requirement, feeds in bad input, and may review your code with you the next day. The section below goes through the reported problems.

03
Problem solving and data structures
30 to 90 minutes, often in a Google Doc

One or two problems at LeetCode-medium level, written without running the code, with the complexity explained. Reported topics include graphs, trees, dynamic programming and intervals.

04
Design
60 to 90 minutes

Low-level or high-level design. Reported prompts include a notification system, a ledger system and a quick commerce system. SDE-1 candidates usually get a second problem solving round instead.

SDE-2 and above
05
Hiring manager
30 to 60 minutes

Your projects in depth, why Flipkart, why you are leaving, how you handle disagreement and deadlines, and what you want to work on.

03

Flipkart machine coding round: problems and how to build them

Reported problems and how to build them

Candidates describe three parts. First, 15 to 30 minutes on the requirements, where you can ask questions. Then about 90 minutes of coding on your own laptop, in any language, sometimes screen-recorded with no interviewer in the room. Then a demo and a review, where the interviewer runs your program, adds a requirement and checks how you handle bad input. The checks reported across sources are: the code runs and the demo works, edge cases and exceptions are handled, the design is modular and object-oriented, a new requirement fits in with a small change, and, at SDE-3, the code is safe when used from several threads. A console program with in-memory data is expected; no database, web server or UI unless you are told otherwise.

  • Conference room allocation: Reported in a two-hour SDE-1 round: buildings, floors and rooms, booked by time slot. Model Building, Floor, Room and Booking, keep each room's bookings in a map from slot to booking, and put the availability check in one method. Edge cases were the main emphasis: overlapping slots, unknown rooms and cancelling a booking that doesn't exist.
  • Interviewer allocation: Reported in an SDE-2 round: two interview types and interviewers with preferred time slots. Make the interview type an interface or enum with its own rules, and pick interviewers with a strategy you can swap. Interviewers then asked how to add a new type or slot, and booked an invalid slot to test exception handling.
  • Food ordering system: Reported in 2024 (SDE-3) and 2025 (SDE-2): restaurants, menus, orders and a rule for which restaurant gets an order. Keep the selection rule (lowest price, best rating) behind one interface. At SDE-3, make order placement and restaurant capacity thread-safe.
  • Text editor with undo and redo: Reported in an SDE-1 round: insert, delete, copy, paste, undo and redo on lines of text. Store each action as a command object with its own undo, keep an undo stack and a redo stack, and clear the redo stack after any new action.
  • Employee bonus rules: Reported in an older SDE-2 round: an employee hierarchy with bonuses for the top performers, then a new rule added live, such as excluding anyone who joined in the last six months. Write each eligibility rule as its own class so the new rule is one more class in a list.
  • Practice problems people use: Splitwise with debt simplification, snake and ladder, a parking lot, a digital wallet and a gym slot booking app are common practice problems for this round. Build each in 90 minutes from a blank project, then add one feature you didn't plan for and see how much code you had to change.
  • Using the 90 minutes: Spend the first minutes listing must-have features and asking about anything unclear. Get the core flow running end to end within the first hour, with sample data loaded at start-up and a simple command loop. Then add validation, then the extras. A working program with fewer features beats a well-designed one that doesn't run.

Calibrd can't watch you code for 90 minutes. It can rehearse the review and the questions around it: explaining your design, the extension, the edge cases and the design round.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Flipkart.

Predict my Flipkart questions →
04

What Flipkart screens for

Flipkart lists five values on its early careers page and says its interviews combine technical, functional and value-based assessments. In its own words:

  • Audacity: we think big and take bold bets
  • Bias for Action: a strong sense of urgency to solve problems strategically
  • Customer First: we look at the world from our customers' point of view
  • Integrity: we strive to do what is right, and do what we say we will do
  • Inclusion: we value the uniqueness of everyone and foster a sense of belonging
05

Flipkart interview questions

Candidate-reported themes

These are the problems and questions candidates report from Flipkart rounds, with practice prompts in our own words where the exact problem isn't public. The machine coding problems change between drives; the checks don't, so practise against the checks.

Behavioural & motivation

  • Why do you want to join Flipkart?
  • Tell me about yourself.
  • Walk me through the code you wrote in the machine coding round. What would you change if you had another hour?
  • Tell me about a time you made a bold technical bet. How did it turn out?
  • Tell me about a disagreement with your manager or a teammate about a technical decision.

How to stop rambling in your answers →

Technical

  • Your meeting room booking system works. Now add a new room type that can only be booked by managers, without editing the classes you already have. Talk through the change.Live extension: Reported in machine coding rounds since 2015: add a new interview type or time slot (SDE-2), add an eligibility rule to a bonus system (SDE-2)Listening for: Where it goes · What stays the same · Proves it
  • A user books slot 9 in a day that has 8 slots, cancels a booking that doesn't exist, and books the same room twice at once. What does your program do in each case?Bad input and edge cases: Reported: the interviewer booked "slot 9" in a day of 8 slots to check exception handling (SDE-2); edge cases were the main emphasis in a 2-hour SDE-1 roundListening for: Validates input · Clear errors · State stays right
  • Two users try to book the last free slot in the same room at the same moment. How does your code make sure only one of them gets it?Concurrency: Reported as essential in SDE-3 machine coding (December 2024); a task scheduler with worker threads appears in SDE-3 reportsListening for: Names the race · A fitting lock · Knows the cost
  • On a 100-square snake and ladder board, find the fewest dice rolls needed to get from square 1 to square 100. Explain the approach before you write it.Problem solving and data structures: Reported: two LeetCode-medium problems in a Google Doc (SDE-2, 2025); the fewest dice rolls on a snake and ladder board (SDE-1)Listening for: Models it as a graph · Breadth-first search · Cost
  • Design the classes for a notification system that sends order updates by SMS, email and push, lets users turn channels off, and retries failed sends.Low-level design: Reported in a 2025 SDE-2 design round: a notification systemListening for: Clean classes · Easy to extend · Retries
  • Design a quick commerce system that promises delivery in about ten minutes from local dark stores. Start with what the customer sees and work back.High-level design: Reported: a ledger system (SDE-2) and a quick commerce system (SDE-3, 90 minutes)Listening for: Scopes it · Live stock · Order to rider
  • Explain how React decides what to change in the DOM when state updates, and why list items need stable keys.UI engineering: Reported in a 2025 UI Engineer 2 loop: async JavaScript, trees and React reconciliationListening for: The diff · Keys · An example

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Flipkart questions →
06

Pay

Flipkart's job listings don't show pay, and the figures on salary sites are self-reported and unconfirmed, so they're left out here. Ask the recruiter for the fixed pay, the bonus and the stock part of any offer separately.

Applying to Flipkart? Paste the posting and see whether they’d shortlist you →

07

How to prepare for a Flipkart interview

  1. Build five machine coding problems from a blank project, 90 minutes each, with a timer: conference rooms, a food ordering app, a text editor with undo, Splitwise and a parking lot.
  2. After each one, have a friend add a rule you didn't plan for, and count how many existing files you had to change.
  3. Write a small project skeleton you can set up in five minutes in your chosen language: models, services, a command loop and sample data.
  4. Feed every program bad input: an unknown ID, a slot out of range, a duplicate booking. It should refuse clearly and never crash.
  5. For SDE-3, make one of your builds thread-safe and be ready to explain where the race was.
  6. Practise LeetCode-medium graph, tree and interval problems on paper or in a plain document, explaining the complexity aloud.
  7. For SDE-2 and above, prepare both a low-level design (classes) and a high-level design (services and data) for one Flipkart-like system.
  8. Prepare one story for each of Flipkart's values, with a number, for the hiring manager round.

This guide covers software engineer hiring at Flipkart in India, from SDE-1 to SDE-3 and UI engineer, plus GRiD for students. Flipkart publishes no experienced-hire interview process, so the rounds come from candidate reports, marked as such. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at TCS, Infosys or Zoho? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Flipkart mock: spoken answers, coached on the spot. Your first mock is free.

Run a Flipkart mock →
08

FAQ & sources

What is Flipkart's interview process?

These rounds are reported by candidates for SDE-1 to SDE-3 roles in Bengaluru between 2024 and 2026, and they match reports going back to 2015. The stages, in order: Online assessment; Machine coding; Problem solving and data structures; Design; Hiring manager.

What does Flipkart look for in candidates?

Flipkart lists five values on its early careers page and says its interviews combine technical, functional and value-based assessments. Audacity; Bias for Action; Customer First; Integrity.

What questions does Flipkart ask in interviews?

These are the problems and questions candidates report from Flipkart rounds, with practice prompts in our own words where the exact problem isn't public. Technical themes: Live extension; Bad input and edge cases; Concurrency; Problem solving and data structures; Low-level design; High-level design; UI engineering.

What happens in the Flipkart machine coding round?

Candidates describe three parts. First, 15 to 30 minutes on the requirements, where you can ask questions. Covered on this page: Conference room allocation; Interviewer allocation; Food ordering system; Text editor with undo and redo; Employee bonus rules; Practice problems people use; Using the 90 minutes.

How do I get a job at Flipkart?

Flipkart hires software development engineers at three levels: SDE-1 (early career), SDE-2 and SDE-3 (senior), plus UI engineers, data scientists and engineers for its quick commerce service, Flipkart Minutes, and its payments app, super.money. In May 2025 it announced 5,000 hires for the year, focused on those two businesses. Hiring runs in 5 stages, starting with Online assessment.

How do I prepare for a Flipkart interview?

Build five machine coding problems from a blank project, 90 minutes each, with a timer: conference rooms, a food ordering app, a text editor with undo, Splitwise and a parking lot. After each one, have a friend add a rule you didn't plan for, and count how many existing files you had to change.

Prep for a real Flipkart role

Practise your Flipkart interview, out loud.

Paste a real Flipkart posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Flipkart prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Flipkart Machine Coding Round and SDE Interview — Calibrd