Flipkart interview research
Candidate accounts · 2 scoped accounts · 11 reported questions/topics
Snapshot: 1 October 2026 · Software/backend focus · No live fetching
Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.
Questions people reported
Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.
Topics in these accounts: Practical coding · Coding · LLD · System design · Behavioral
SDE II backend; Bengaluru; July 2025
Read the original candidate account
Scope and source limitations
The stated logarithmic tree target is tied to the source's special constraints; it is not a general guarantee for arbitrary trees.
Executable conference-room reservation service
Practical coding · Reported topic
Second-smallest value in a specially ordered binary tree
Coding · Reported topic
Ingredient dependencies and feasible preparation order
Coding · Reported topic
Auditable customer-issue workflow
LLD · Reported topic
Airline reservation schema and concurrent seat allocation
LLD · Reported topic
SDE II; location unknown
Read the original candidate account
Scope and source limitations
Report published July 8, 2025; exact interview date not given. This is independent of the other Flipkart backend report.
Shopping bill, discounts and reward tiers
Practical coding · Reported topic
Rightmost deepest leaf in a complete binary tree
Coding · Reported topic
Smallest missing nonnegative value
Coding · Reported topic
Decompose dictionary entries into other dictionary words
Coding · Reported topic
Racing-game leaderboard and timely notifications
System design · Reported topic
Recent technical work and disagreements
Behavioral · Reported topic
Additional independent, matching role/level/region reports are needed before claiming recurring patterns.
A suggested 14-day preparation plan
Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.
Backend correctness and Java/SQL depth
Balance DSA with transactions, indexes, API contracts, Java fundamentals, concurrency and failure recovery.
- Days 1–2: hashing, prefix sums and interval/window exercises.
- Days 3–4: Java collections, object contracts and concurrency tests.
- Days 5–6: SQL joins/indexes; transaction isolation and locking examples.
- Days 7–8: implement a reservation, ledger or workflow service.
- Days 9–10: design retries, idempotency and asynchronous failure recovery.
- Days 11–14: design mock, project debugging story and mixed final mock.
Practise an original design exercise
Design a sale checkout service with limited stock.
This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.
How this research was collected
Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.