What Flipkart actually tests, round by round

I opened Flipkart’s official How We Hire page on 6 September 2026 and counted the stages it lists for the Flipkart interview process: application, screening, an optional technical phone screen, onsite interviews, a hiring committee review, an offer, and onboarding. Seven steps, no numbers attached to any of them. No mention of what a machine coding round is, how long the loop takes, or how campus hiring differs from lateral hiring. That gap is the whole reason this post exists.

Flipkart is one of the largest tech employers in India, and its interview loop for SDE roles is one of the few in the country built around a proper low-level design round rather than pure algorithm trivia. Most prep content treats it like a LeetCode contest. It isn’t.

Why the Flipkart interview process is hard to research online

Search for the Flipkart interview process and you get a wall of near-identical listicles, most of them scraped from the same four or five candidate write-ups, repackaged with a new headline each quarter. None of them separate campus timelines from lateral timelines. Almost none mention that non-engineering roles skip machine coding entirely and run a case exercise instead. This post pulls from Flipkart’s own hiring page plus the interview reports that actually match each other, and says plainly where the record runs thin.

Flipkart’s How We Hire page describes an application review, then says a recruiter will be assigned to your profile, then a technical screening that the page calls optional depending on role, then onsite rounds, then a hiring committee that makes a collective call on your performance rather than a single interviewer. That committee detail is worth sitting with. A hiring manager who liked you can still get overruled, and one bad round rarely sinks you alone if the rest of the loop was strong.

What the page does not say: how many onsite rounds, what a machine coding round involves, or what separates an SDE-1 loop from an SDE-2 loop. For that you need the interview reports candidates post after the fact, and those reports are consistent enough across sources to trust.

The Flipkart interview process for SDE roles, round by round

For SDE-1 and SDE-2 hiring, candidates report four to five rounds spread across three to four weeks: an online coding assessment, one or two live data structures and algorithms rounds, a machine coding round, and (for SDE-2 and above) a system design round, closing with a hiring manager or HR conversation. A GeeksforGeeks-hosted account from an SDE-2 candidate with 3.5 years of experience lists this exact sequence, and it matches what several other logged experiences describe for the same band.

The DSA rounds look like what you would expect from any product company: arrays, graphs, dynamic programming, occasionally a follow-up on time complexity that punishes a brute-force answer given without acknowledging it’s brute force. Nothing unusual. The unusual part comes next.

The machine coding round nobody explains properly

This is the round that fails people, and it fails them for a reason that has nothing to do with algorithms. Machine coding at Flipkart gives you a real-world system to build in a code editor, not a whiteboard sketch. One documented format, described in a candidate’s LeetCode discuss post, is 30 minutes of the interviewer explaining the problem followed by 90 minutes of actual coding, with no restriction on language.

Recent problems candidates report include a stock-tracking platform with order placement and basic portfolio tracking, and an e-commerce loyalty system with points, levels, and redemption logic. Design a small platform, not a function. You’re expected to write classes, use interfaces where they make sense, and produce code that runs and extends cleanly if the interviewer asks you to add a feature in the last ten minutes, which they usually do.

Here’s what actually gets you cut: writing working code with no structure at all, and writing beautiful abstractions that don’t run. Flipkart’s interviewers have said in multiple write-ups that they weight running, extensible code over pretty code that fails on the follow-up ask. Practice ten to fifteen machine coding problems before your loop, and time yourself at two hours per problem including a requirement change halfway through. If you’ve never done one, our system design interview guide covers the conceptual half of this; the coding half you can only build by doing it under a clock.

Campus hiring runs on a different clock than lateral hiring

Flipkart hires through three tracks that don’t get compared often enough: standard campus and off-campus recruiting, Runway, a dedicated drive for candidates from non-traditional backgrounds and career breaks, and GRiD, its coding contest that feeds directly into interview shortlists for students. Campus loops tend to compress: an online assessment, then two to three technical rounds on the same day or over a single visit, because colleges book Flipkart for a fixed window and everyone gets processed in it.

Lateral hiring is slower and lonelier. You’re one applicant moving through a recruiter’s queue, rounds get scheduled around your interviewer’s calendar rather than a campus event, and the 21 to 30 day timeline candidates report for the SDE loop is closer to normal for experienced hires than for freshers, who often hear back within a week of their campus event because the whole cohort gets ranked together.

If you’re coming in lateral, follow up with your recruiter after 10 business days of silence. Not before. Recruiters are managing dozens of loops and a message on day three reads as anxious rather than proactive.

Non-engineering roles: a different loop, same committee structure

Product, category management, supply chain and operations roles at Flipkart skip the machine coding round entirely and replace it with a case-style exercise: a business problem, sometimes with real Flipkart data shown anonymized, where you’re asked to size an opportunity or diagnose a metric drop. The hiring committee structure still applies here. An interviewer who loved you doesn’t get final say on their own.

For these roles the DSA prep is pointless and the case prep is everything. Practice structuring an answer out loud before you get a number, because interviewers cut people off who reach for a number too early and can’t explain the assumption behind it.

What to actually do in the last two weeks

Two weeks is enough time to fix the machine coding gap if that’s your weak point, and it isn’t enough time to relearn dynamic programming from scratch. Triage honestly. If your DSA rounds have historically gone fine and machine coding is new to you, spend twelve of your fourteen days there: five practice problems in week one, five in week two, each timed at two hours with a requirement change added at the 90 minute mark by whoever is running your mock.

Mock the hiring manager and HR conversation too. It gets skipped in most prep plans because it feels like a formality, and then candidates freeze when asked why they want to leave their current role or what they’d change about a project they shipped. Our STAR method examples post has a format that holds up in that specific conversation, and our notice period guide is worth reading before that call too if you’re coming from an Indian IT services company, since Flipkart’s HR will ask about it directly.

One thing I’d push back on: a lot of prep advice tells candidates to over-prepare behavioral answers until they sound rehearsed. At Flipkart specifically, interviewers on the hiring committee compare notes, and a canned answer that doesn’t match the tone of your actual project conversation reads as a red flag rather than polish. Practice the structure. Don’t memorize the sentences.

I don’t have a clean number for what fraction of candidates fail specifically at machine coding versus DSA. Nobody publishes that. What the reports agree on is that it’s the round people are least prepared for relative to how heavily it’s weighted, and that alone is worth two weeks of your attention.

What to know on interview day itself

A few smaller things worth knowing before you walk in. Flipkart’s onsite loops, whether in Bangalore or remote, are usually run over video even for local candidates, so test your setup a day ahead rather than five minutes before. Interviewers take written notes throughout and read from them in the hiring committee meeting, so a strong verbal answer that never got said out loud does not exist on the record. If English is not your first language and the interview makes you nervous mid sentence, say so and slow down. Nobody has ever been marked down at Flipkart for asking an interviewer to repeat a question.

Do referrals actually help?

A referral does not skip any round at Flipkart, and the hiring committee still reviews your performance the same way. What it can do is get a recruiter to look at your resume sooner, which matters more than people think when a job posting has thousands of applicants within days. If someone you know works there, ask them to submit your resume before you apply cold. It costs nothing and the downside is zero.