Flipkart SDE-2 Bangalore 2024: Wallet Machine Coding, Two LeetCode Hards, Spotify System Design, Offer

TL;DR. Applied to Flipkart in January 2024. Recruiter reached out in March. Four rounds completed by May: a 2.5-hour machine coding round (design a wallet system in Java), a DSA round with two LeetCode hards (Longest Valid Parentheses and Maximum Performance of a Team), a system design round (design JukeBox/Spotify covering API design, schema, and database indexing), and a hiring manager round that was conducted twice because the first attempt hit a CGPA discussion that needed rescheduling. Offer received for SDE-2 at Flipkart Bangalore.

This is not a "Flipkart interview preparation roadmap." This is one lateral candidate's specific 2024 loop, with the exact machine coding problem, the exact DSA questions, and the exact system design prompt. If you are interviewing at Flipkart for SDE-2, the machine coding format and the HM round dynamics here are the practical signal that prep blogs do not cover.

The candidate

The candidate does not disclose their previous company, years of experience, or current compensation. The SDE-2 targeting and lateral hiring channel indicate at least 2 to 4 years of industry experience, consistent with Flipkart's SDE-2 band. The 2-month gap between application (January) and recruiter contact (March) is standard for Flipkart's lateral hiring pipeline, which processes a high volume of SDE-2 applications.

Timeline: January Application to May Offer

A 4-month timeline from application to offer is typical for Flipkart SDE-2 lateral hiring. The bottleneck is not the interview rounds themselves (those complete in 2 to 3 weeks once scheduling starts). The bottleneck is the initial screening queue. Flipkart receives thousands of SDE-2 applications per quarter, and the recruiter screening funnel operates with a 60 to 90 day lag.

Practical takeaway: if you apply to Flipkart and hear nothing for 8 weeks, that is normal. Do not withdraw or re-apply. The re-application resets your position in the queue. If you have a referral, use it at application time, not as a follow-up, because the referral tag accelerates the screening stage specifically.

Round 1: Machine Coding, Design a Wallet System (2.5 Hours)

This is Flipkart's signature round. No other major Indian tech company runs a 2.5-hour machine coding round with this structure. The format is split into three phases:

Phase 1: Design discussion (30 minutes). The interviewer presents the wallet system requirements. You discuss entities (User, Wallet, Transaction, Balance), relationships, and key behaviors (credit, debit, transfer between wallets, balance query, transaction history). The interviewer evaluates whether you ask clarifying questions before designing. "What happens on insufficient balance?" "Are transfers atomic?" "Is transaction history bounded or unbounded?" These questions separate SDE-2 candidates from SDE-1 candidates.

Phase 2: Coding (90 minutes). You implement the wallet system in your chosen language. The interviewer expects:

• Clean class hierarchy with proper encapsulation
• Transaction atomicity (debit + credit in a transfer should not leave the system in a half-state)
• Meaningful error handling (InsufficientBalance, InvalidUser, DuplicateTransaction)
• At least 5 to 8 test cases written by you, covering: basic credit, basic debit, insufficient balance debit, self-transfer rejection, concurrent transfer handling (discussion-level, not necessarily thread-safe code), and transaction history ordering

Phase 3: Review (30 minutes). The interviewer walks through your code, asks about design decisions, proposes extensions ("what if we add recurring payments?" or "what if we need daily balance snapshots?"), and evaluates whether your class design can accommodate extensions without major rewrites.

The candidate used Java. Flipkart's machine coding rounds accept any language, but Java is the most common choice because Flipkart's backend is primarily JVM-based. Using Python is acceptable but puts you at a slight disadvantage in discussions about type safety, interface design, and concurrent data structures.

Preparation that works for this round. The candidate mentions practicing Snake and Ladder and Restaurant Booking system implementations. These are the two most commonly recommended machine coding practice problems in the Indian SDE-2 interview circuit. Others worth practicing: Splitwise (expense splitting), Parking Lot (multi-level with vehicle types), and Library Management System. The common thread is: multiple entity types, at least one transactional operation, and a requirement for clean OOP boundaries.

Do not practice by reading LLD solutions on GeeksforGeeks. Practice by implementing them end-to-end in an IDE with test cases, within a 90-minute time box. The difference between "I understand the wallet system design" and "I can implement a working wallet system in 90 minutes with test cases" is the difference between rejection and offer at Flipkart.

Round 2: DSA, Two LeetCode Hards (1 Hour)

Two hard problems in 60 minutes. This is Flipkart's standard DSA round intensity for SDE-2.

Problem 1: Longest Valid Parentheses. Given a string containing only ( and ), find the length of the longest valid (well-formed) parentheses substring.

Three approaches exist:

• Stack-based (optimal for interviews): Push indices onto a stack. When you see ), pop the stack. If the stack is empty, push the current index as a new base. If not empty, the current valid length is current_index - stack.top(). Track the maximum. Time O(n), space O(n).
• DP: dp[i] = length of longest valid substring ending at index i. If s[i] == ')' and s[i-1] == '(', then dp[i] = dp[i-2] + 2. If s[i] == ')' and s[i-1] == ')' and s[i - dp[i-1] - 1] == '(', then dp[i] = dp[i-1] + 2 + dp[i - dp[i-1] - 2]. Time O(n), space O(n).
• Two-pass counter: Scan left-to-right counting open and close. When equal, record length. When close exceeds open, reset. Then scan right-to-left with mirrored logic. Time O(n), space O(1). Elegant but harder to explain clearly in an interview.

The stack-based approach is the safest interview choice because it is intuitive to explain, easy to trace through examples, and has clean edge case handling.

Problem 2: Maximum Performance of a Team. Given n engineers with efficiency and speed values, choose at most k engineers to maximize performance = sum(speed) * min(efficiency).

The standard approach:

• Sort engineers by efficiency in descending order.
• Iterate through the sorted list. For each engineer, add their speed to a running sum. If the number of selected engineers exceeds k, remove the one with the smallest speed (use a min-heap of size k).
• At each step, compute performance = speed_sum * current_efficiency (current efficiency is the minimum because we are iterating in descending efficiency order). Track the maximum.

Time: O(n log n) for sorting + O(n log k) for heap operations. Space: O(k) for the heap.

This is a classic greedy-with-heap problem. The trick is sorting by one dimension (efficiency, descending) and greedily managing the other dimension (speed) with a heap. If you have not seen this pattern before, it is nearly impossible to derive in a 30-minute window. Drill the "sort by one, heap the other" pattern before any SDE-2 interview.

The interviewer provided hints. At Flipkart, hints are not penalized as heavily as at Google. The interviewer is evaluating whether you can take a hint and converge on the solution, not whether you can solve the problem independently. If a hint leads you to the correct approach within 5 minutes, that counts as a pass. If you need 3 hints and still cannot converge, that is a fail.

Round 3: System Design, Design JukeBox/Spotify (1 Hour)

Flipkart's SDE-2 system design round is a hybrid: it expects both high-level architecture (services, data flow, scaling) and low-level specifics (API contracts, database schema, index design). This is different from Google or Amazon, where HLD and LLD are separate rounds.

What the interviewer expects for "Design Spotify" at SDE-2 level:

Functional requirements: User registration and authentication, browse/search songs by title/artist/album/genre, create and manage playlists, play a song (streaming), like/save songs, recommendations (basic).

API design (3 to 5 core endpoints):

• GET /songs?q={query}&page={n}: search with pagination
• GET /songs/{id}/stream: returns a streaming URL or chunked audio response
• POST /playlists: create a playlist
• PUT /playlists/{id}/songs: add/remove songs from a playlist
• GET /users/{id}/recommendations: personalized song recommendations

Schema design:

• users(id, name, email, created_at)
• songs(id, title, artist_id, album_id, genre, duration_sec, audio_url, created_at)
• artists(id, name, bio, image_url)
• albums(id, title, artist_id, release_year, cover_url)
• playlists(id, user_id, name, created_at)
• playlist_songs(playlist_id, song_id, position, added_at)
• user_likes(user_id, song_id, liked_at)

Database indexing (this is where Flipkart goes deeper than most companies):

• Composite index on songs(artist_id, title) for artist-specific searches
• Full-text index on songs(title) + artists(name) for general search
• Index on playlist_songs(playlist_id, position) for ordered playlist retrieval
• Index on user_likes(user_id, liked_at DESC) for "recently liked" feed

The indexing discussion is the differentiator. At SDE-1, Flipkart accepts "we'll add indexes as needed." At SDE-2, they expect you to name specific indexes, explain the column order, and justify why a composite index on (artist_id, title) is better than two separate indexes for this query pattern.

Scaling discussion: Audio streaming should be CDN-backed (Cloudflare, Akamai). Metadata queries hit a read replica. Search should be backed by Elasticsearch or Solr, not raw SQL LIKE queries. Recommendation engine is a separate service, can be eventually consistent, backed by a collaborative filtering model pre-computed in batch.

Round 4: Hiring Manager, Conducted Twice

The hiring manager round was conducted twice. This is unusual but not unprecedented at Flipkart.

Attempt 1. The first HM round focused on academic background and CGPA. The candidate received "callouts" (critical feedback) on academic performance. This led to a reschedule. The most likely scenario: the first hiring manager was from a team that weighted academic credentials heavily (some Flipkart teams, particularly in platform engineering, have this preference), and the candidate's profile did not match that team's bar. The recruiter rescheduled with a different team's HM.

Attempt 2. The second HM round was with a senior engineering manager and focused on project discussion. The candidate walked through their previous work, architectural decisions, and trade-offs. This round resulted in selection.

This dynamic reveals an important aspect of Flipkart's hiring process: the hiring manager round is team-specific. Different teams at Flipkart have different bars for SDE-2. A team working on supply chain optimization may care about your experience with distributed transactions. A team working on ads may care about your experience with real-time bidding systems. A team working on seller tools may care about your experience with CRUD-heavy enterprise systems. If the first HM round feels like a mismatch, a reschedule with a different team is possible, and the recruiter can facilitate this.

Practical takeaway: before the HM round, ask the recruiter which team you are being matched with and what that team's current focus areas are. Tailor your project discussion to align with those focus areas. If you worked on a payments system and the team works on payments, lead with that. If you worked on a recommendations engine and the team works on search, find the overlap in infrastructure patterns (both involve ranking, both involve real-time scoring, both involve AB testing).

Preparation Resources Named by the Candidate

The machine coding resources are worth expanding. The standard Flipkart machine coding preparation set (recommended across multiple verified experiences) includes:

1. Snake and Ladder: Multi-player board game with dice rolls, snakes, and ladders. Tests: entity modeling (Board, Player, Dice, Snake, Ladder), game loop design, winner detection logic.
2. Restaurant Booking: Time-slot based reservation system with table capacity management. Tests: conflict detection, overbooking prevention, cancellation handling.
3. Splitwise: Expense sharing with group and individual balance tracking. Tests: graph-based simplification of debts, transaction atomicity.
4. Parking Lot: Multi-level, multi-vehicle-type parking with pricing. Tests: strategy pattern for pricing, factory pattern for vehicle creation.
5. Wallet System (the actual question in this loop): Credit, debit, transfer, balance, transaction history.

Implement all 5 in your interview language, with test cases, within 90-minute time boxes. If you cannot complete any of them in 90 minutes, you are not ready for Flipkart's machine coding round.

What the wallet round reveals about Flipkart hiring

1. Flipkart's machine coding round is the differentiator. No other major Indian tech company runs a 2.5-hour implementation round at SDE-2. If you can build a clean, tested, extensible system in 90 minutes of coding time, you are likely passing 3 of Flipkart's 4 rounds. If you cannot, no amount of DSA prep compensates.

2. Two LeetCode hards in 60 minutes is the DSA bar at SDE-2. You need to solve each in under 30 minutes. This requires pattern recognition, not brute-force derivation. Drill the "sort by one dimension, heap the other" pattern, the stack-based parentheses/brackets family, and the greedy-with-priority-queue family until they are reflexive.

3. System design at Flipkart goes deeper on database internals than Google or Amazon. Expect to name specific indexes, justify column ordering in composite indexes, and discuss trade-offs between full-text search engines and SQL LIKE queries. Read about B-tree index mechanics, composite index column ordering, and covering indexes before your round.

4. The hiring manager round is team-specific, and a mismatch is recoverable. If the first HM round does not go well due to a team-fit mismatch (not a technical failure), the recruiter can reschedule with a different team. This is not guaranteed, but it is more common than candidates expect. Ask the recruiter about the team before the HM round.

5. Application-to-recruiter lag is 60 to 90 days. Do not interpret silence as rejection. The screening queue is long. A referral accelerates this stage specifically.

6. Hints in the DSA round are not penalties. Flipkart evaluates whether you can take a hint and converge, not whether you can solve independently. If a hint unlocks your approach within 5 minutes, you are still on track.

What lateral candidates ask about Flipkart SDE-2

What is Flipkart SDE-2 compensation in Bangalore? Flipkart SDE-2 total compensation in Bangalore typically ranges ₹28L to ₹42L. The structure is base salary (₹18L to ₹24L), stock units (vesting over 4 years, significant variability), and performance bonus (up to 10% annually). Signing bonuses are sometimes offered for strong competing offers.

Is the machine coding round always 2.5 hours? Yes, for SDE-2 and above. SDE-1 machine coding rounds at Flipkart are shorter (60 to 90 minutes) and have simpler problem scopes.

Can I use Python for the machine coding round? Yes, any language is accepted. Java is the most common choice because of Flipkart's JVM backend. Python is fine but requires you to demonstrate OOP discipline (using classes and proper encapsulation rather than scripts with dictionaries).

How many LeetCode hards should I prepare? The DSA round pulled from two distinct patterns: stack-based string processing and greedy-with-heap optimization. Prepare at least 30 hard problems across 6 to 8 patterns: stack, heap+greedy, DP (1D and 2D), graph (shortest path, topological sort), tree DP, sliding window, binary search on answer, and segment tree/BIT basics.

What if the first HM round goes badly? If the failure is a team-fit mismatch rather than a technical failure, a reschedule with a different team is possible. Communicate with the recruiter. If the failure is on behavioral grounds (cannot explain previous work, poor communication), a reschedule is unlikely.

Verification and source

This analysis is built on a verified interview experience published on Medium by Anmol Mittal. Original source: Flipkart Interview Experience for SDE-2

PapersAdda's verification standard requires a publicly accessible post URL, per-round detail from the candidate, and a stated outcome. This post meets all three criteria. The candidate specified the exact machine coding problem (wallet system), the exact DSA questions (Longest Valid Parentheses and Maximum Performance of a Team by name), the system design prompt (JukeBox/Spotify), and the hiring manager round dynamics (two attempts). The timeline of January application to May offer is explicitly stated in the source.

Related verified interviews

• The Google alternative (same seniority, different outcome): Google L4 Bangalore April 2025, topological sort to 12-month cooldown, where 4 rounds at L4 ended in rejection despite strong Googlyness
• Another Google rejection at L4: Google L4 India, 7 rounds, Strong Hire phone screen, downleveled then rejected, the 7-round marathon that collapsed after a recruiter said "100%"
• Amazon's L5 loop for comparison: Amazon SDE-2 L5 2026, Tier-3 engineer's real 5-round loop to ₹60L, same seniority band but recruiter-initiated, not application-initiated
• Earlier career at Amazon: Amazon SDE-1 onsite 2026, Tier-2 engineer's real 4-round loop, the SDE-1 equivalent for comparison
• Microsoft for freshers: Microsoft explore internship 2026 prep strategy real, the early-career entry point at a different FAANG

Related: LeetCode questions asked in TCS 2026, for the verified question-frequency analysis and pattern-wise prep approach.

How we keep this current: the patterns and figures here are compiled from public candidate reports and official notifications. Treat specifics as candidate-reported rather than official, and confirm cut-offs, dates, and eligibility on the official portal before you rely on them.