Flipkart vs Amazon India Interview: Two Very Different Tests

You're applying to both Flipkart and Amazon India at the same time. Smart. Efficient. Also, a little chaotic. Because these two companies, which operate in the same country selling some of the same products, have designed interview loops that have almost nothing in common beyond "there will be code."

Flipkart's signature is a 90-minute machine coding round where you build a working object-oriented system from scratch, submit a zip file, and pray. Amazon India's signature is a behavioral track woven through every single round, where 25% of candidates who clear the technical bar still get rejected because their Leadership Principles stories don't hold up when someone starts asking follow-up questions.

Same domain. Completely different tests.

Flipkart vs Amazon India: Rounds at a Glance

Stage	Flipkart	Amazon India
Online Assessment	90 min, 3 DSA problems (HackerRank)	70 min, 2 coding problems + 50+ behavioral (HackerRank)
Technical Round 1	PSDS-1: DSA, 60 min, Google Doc	Technical + 2-3 LP questions, 60 min
Technical Round 2	PSDS-2: DSA (if PSDS-1 passes), 60 min	Technical + 2-3 LP questions, 60 min
Signature Round	Machine Coding: 120 min LLD	Bar Raiser: LP-heavy, may have no coding
Design Round	System Design (SDE-2+): HLD + LLD	System Design (SDE-2 loop): HLD
Final	Hiring Manager + HR	Hiring Manager

End to end, Flipkart takes roughly three to five weeks. Amazon's loop typically wraps in two to three weeks once the OA clears.

Inside the Flipkart Loop

The PSDS Rounds Are Warmer Than You Expect

Flipkart's Problem Solving and Data Structures rounds happen in a shared Google Doc. No compiler, no IDE, no autocomplete nagging at you. Just you, the interviewer, and a blank text editor that doesn't even have syntax highlighting.

The interviewer is evaluating your thinking process, not your ability to pass a compiler. Pseudocode is fine as long as your reasoning lands. That said, if your first approach is naive, expect harder follow-ups. Don't coast.

Common patterns: sliding window, two pointers, prefix sums, trees, heaps, and dynamic programming. Difficulty lands at LeetCode medium-hard. A typical PSDS-1 has one easier problem and one harder one in 60 minutes. If PSDS-1 goes well, PSDS-2 follows within the same week and usually dials up the difficulty.

The Flipkart Machine Coding Round Is the Real Filter

This is the round that defines Flipkart's loop. You get one object-oriented design problem and 90 minutes to write working, extensible code. Then 30 minutes of discussion with the interviewer.

The rules:

Any language is fine (most candidates use Java or Python)
No external databases. Everything in-memory: HashMap, ArrayList, HashSet
You submit a zip file via a Google Form when time is up
The code must run. It must also be readable and defensible

Recent problems from the machine coding round include:

Coding Blox: an online competitive programming platform where users sign up, create contests with difficulty tiers, and participate in contests run by others
Wallet System: load money, send to users, check balance, transaction history with sorting and filtering
Doctor Appointment Booking: doctors declare availability, patients search by specialty and book
Distributed Task Scheduler: workers pick up tasks, dynamic load balancing, task retry on failure

Notice the pattern. Every problem is a small production system. Not a trick puzzle. A real-world domain with entities, behaviors, and interactions. You're not solving an edge case hunt. You're building something that could ship.

Flipkart prioritizes running code over pristine architecture. If you have to choose between a working solution with messy design patterns and a beautiful but broken design, submit the working one. The 30-minute discussion is where you defend your choices, so at least understand why you made each decision.

The four design patterns that appear most frequently: Strategy, State, Factory, and Observer. Learn these four and you can reach for the right tool on most problems.

A meme showing a programmer confidently submitting code labeled "it works!! don't touch!!!" with chaotic internals

Every Flipkart machine coding submission after minute 80.

For a deeper look at Flipkart's full process, see the Flipkart software engineer interview guide.

System Design (SDE-2 and Above)

For mid-level roles, you get both LLD and HLD in one round. The expectation is that you drive the scope discussion yourself. Ask about user scale, geographic reach, and consistency requirements before touching any diagram. Interviewers explicitly want you to ask a lot of questions, so go ahead and ask them.

LLD comes first: class schema, database tables with normalization, API signatures. HLD follows: service decomposition, Kafka queues between services, caching layers.

Be ready to defend every schema decision. If you put something in a table, know why it's there and why it's not somewhere else.

Inside the Amazon India Loop

The OA Has Two Distinct Parts (One of Them Will Surprise You)

The Amazon online assessment is longer than most. Two coding problems in roughly 70 minutes on HackerRank, plus a work simulation with 50+ behavioral questions in multiple-choice format.

The behavioral section trips people up because it looks trivial. It isn't. Amazon uses it to filter for LP alignment before you ever talk to a human. Common scenarios: email chains with ambiguous instructions, escalating conflicts with a teammate, tradeoff decisions under resource constraints. For each one, you pick the most and least likely action you'd take. There's no "right answer" listed. There is, however, a right answer.

Every Technical Round Also Has LP Questions. Every. Single. One.

Here's what separates Amazon from almost every other loop. Each interviewer is assigned two or three Leadership Principles to probe. Technical questions and LP questions happen in the same 60-minute round. You are not getting a break from your behavioral prep just because you're explaining a graph traversal.

A typical structure: 20-25 minutes on a DSA problem, then LP questions for the remaining 30-35 minutes. The LP portion isn't an afterthought. It's half the round.

Leadership Principles carry roughly 50% of the decision weight at Amazon. Interviewers formally score both dimensions. Both scores feed into the hire recommendation. If your LP answers are weak, your graph traversal won't save you.

DSA at Amazon India trends toward LeetCode medium difficulty, with occasional hard problems for SDE-2. Common patterns: graphs, hash maps, sliding window, trees. The problems often have an implicit systems context, like "you have a stream of log events, find the top K errors in a rolling window." Part of the challenge is recognizing the algorithm under the scenario description.

See the Amazon software engineer interview guide for the full breakdown of rounds, levels, and what each interviewer is actually scoring.

The Bar Raiser Round Is the Final Boss

The Bar Raiser is a specially trained interviewer from a different team. Their mandate: ensure every new hire raises the bar above the median of the existing team. They hold veto power over any hire recommendation. Any recommendation. From any other interviewer.

The Bar Raiser round is often entirely behavioral. No coding. Two Leadership Principles in extreme depth, with follow-ups designed to stress-test your stories. "What would you have done if your manager had disagreed?" "What did you learn, and how did you change your approach afterward?" "Walk me through the specific technical decision, not the general one."

If your STAR stories are rehearsed but shallow, the Bar Raiser will find the floor. They have one job. They are very good at it. Prepare three or four strong career stories and know every detail of each one. Different LPs can draw from the same story as long as the emphasis shifts.

The three LPs that come up most for SDEs: Ownership, Deliver Results, and Invent and Simplify.

A meme labeled "conflictResolved" showing a confident programmer after solving a conflict

Bar Raiser: "Tell me about a time you had a conflict with a teammate." Your STAR story, if you prepped:

DSA: How Do the Difficulties Compare?

Both companies aim at LeetCode medium-hard. But the shape of "hard" is different.

Flipkart's PSDS rounds tend toward problems where the key insight is a clean algorithmic pattern: a specific data structure choice, a traversal approach, a DP recurrence. The interviewer often nudges you if you're stuck. It's adversarial in difficulty, not in spirit.

Amazon's technical rounds layer systems context onto the algorithm. The problem might technically be a sliding window, but you have to extract that from a scenario description about event logs or inventory tracking. Pattern recognition under light obfuscation is the actual skill being tested.

For both companies, these patterns matter most: arrays and strings, trees and graphs, dynamic programming, heaps and priority queues, and hash maps. For Amazon, also practice problems with a stream or event-driven framing. For Flipkart, practice problems that live at the LLD/algorithm boundary (LRU cache, task scheduler internals, rate limiting).

The DSA guide for backend engineers covers the patterns most relevant to both loops.

How to Prepare for Each

Preparing for Flipkart

Spend at least four weeks on machine coding. Practice building complete systems from scratch with a 90-minute timer. Pick a problem (appointment booking, parking lot, library management), open a blank editor, and build it end to end. Then spend 20 minutes reviewing what you'd change. The timer matters. Reviewing matters. Skipping both is how you show up on round day and realize you've never actually finished one of these.

Study the four key design patterns: Strategy (interchangeable algorithms), State (behavior changes with object state), Factory (decouple object creation), Observer (event-driven updates). Map each pattern to a machine coding scenario so you can reach for the right tool quickly.

For DSA, 30-40 LeetCode mediums across the core patterns is enough. Focus on fluency, not coverage. Brush up on database normalization too. The SDE-2 system design round will ask you to defend your schema, and interviewers probe 1NF/2NF/3NF knowledge.

Preparing for Amazon India

Write your LP stories before you touch a LeetCode problem. This is the part candidates skip, and it's the part that kills them.

For each of the 16 Leadership Principles, write a specific story from your work history in STAR format. Your goal is five to six strong stories that can flex across multiple principles by shifting the emphasis. A story about fixing a production bug under pressure can serve Ownership, Deliver Results, or Bias for Action depending on what you highlight.

Practice answering LP questions out loud. Amazon interviewers ask follow-ups for five to eight minutes per story. If you've only rehearsed the written version, you won't survive the real version. A tool like SpaceComplexity can help you run realistic mock interviews where you get rubric-based feedback on your spoken communication, not just whether you got the algorithm right.

For DSA, 50 LeetCode mediums across graphs, trees, arrays, and hash maps is the baseline.

A Six-Week Timeline for Both

If you're targeting both simultaneously:

Weeks 1-2: DSA fundamentals and medium problems (shared prep for both)
Week 3: Write all LP stories, drill STAR format out loud
Week 4: Machine coding practice (two to three full problems with timer)
Week 5: System design concepts, mock LP interviews
Week 6: Full mock interviews for both formats

Which Should You Target First?

Target Flipkart first if you have strong OOP and design instincts but haven't built a strong behavioral story bank yet. Flipkart's process rewards technical skill more directly. A great machine coding round can carry you past a mediocre DSA round. There's no LP equivalent waiting to veto you at the end.

Target Amazon first if you have strong behavioral stories and solid DSA, but haven't practiced LLD-heavy machine coding. Amazon's loop has more room to recover from a weaker round because you're being evaluated across many dimensions. One rough technical round doesn't end things if your LP answers are strong.

Companies in India sometimes share timelines through recruiting networks. Run them in parallel when you can.

Key Takeaways

Flipkart's defining round is machine coding: 90 minutes, one OOP design problem, working runnable code, no external databases
Amazon India's defining element is Leadership Principles woven through every round, including a dedicated Bar Raiser with veto power
DSA difficulty is similar (LeetCode medium-hard), but Amazon problems layer systems context onto algorithms
For Flipkart, practice building complete systems under time pressure. The four patterns that cover most problems: Strategy, State, Factory, Observer
For Amazon, prepare LP stories before DSA prep. Shallow rehearsed stories break under Bar Raiser follow-ups