Frontend interview guide
Flipkart
India's largest e-commerce platform. Scale defined by Big Billion Days — a frontend that handles crore-user bursts.
Frontend engineers interviewing at Flipkart — consumer web, seller tooling, PhonePe-adjacent surfaces. React/TypeScript.
Last reviewed 2026-10-04
What they emphasise
- Scale under India network conditions — slow mobile is the primary network, not an edge case.
- Dense product-listing UI — filters, pagination, fast scroll.
- DSA bar — the loop is historically algorithmic.
- Big Billion Days — the mental model is 'what happens at 100x traffic'.
The loop, round by round
5 rounds. Durations and formats are typical, not guaranteed — confirm the loop shape with your recruiter in the screen.
Round 1
Recruiter screen
~30 minCallWhat it covers
- Resume, level, team orientation.
- CTC alignment.
What they're looking for
- A specific "why Flipkart" rather than FAANG-generic.
Round 2
Online assessment
~90 minHackerRank / HackerEarthWhat it covers
- 2-3 algorithmic problems.
What they're looking for
- All problems passing all tests within the time.
Round 3
Technical rounds (two)
60 min eachLive coding on videoWhat it covers
- Algorithmic + a UI/React round for FE roles.
What they're looking for
- Correctness with complexity.
- Clean React code and iteration.
Round 4
System design
60 minWhiteboard / shared docWhat it covers
- A frontend-shape prompt — a product listing page, a cart, an Order Tracking surface.
What they're looking for
- Honest treatment of mobile-first scale.
- Awareness of ISR / caching for SEO-sensitive pages.
Round 5
Hiring manager / managerial
45 minConversationWhat it covers
- Behavioural + a system / design question.
- Team scope.
What they're looking for
- Specific stories.
- Ownership framing.
What each level expects
The bar you're being measured against — plus the failure modes candidates most often trip on at that level.
SDE 2 / mid
~2-4 yearsSDE 2 — ships features end to end.
What they expect
- Clean React, DSA fundamentals, mobile-perf intuition.
Common failure modes
- A UI build that ignores mobile network realities.
Senior
~5-8 yearsOwns a technical area.
What they expect
- A system-design round that treats Big Billion Days scale realistically.
- Past-work stories with specific numbers.
Common failure modes
- Textbook pattern recall.
Staff
~8+ yearsMulti-team technical direction.
What they expect
- Peer-level discussion.
- Multi-team leverage.
Common failure modes
- Senior+ output rather than Staff leverage.
How to crack it
Day-of advice. The specific moves that separate offers from no-offers when the content is already in your head.
- 1Prep for mobile-first scale explicitly. Images, bundle size, slow-network behaviour.
- 2Keep DSA fundamentals sharp — the loop is explicit about it.
- 3In the system-design round, name the Big Billion Days scenario and design for it (CDN caching, ISR, image strategy, graceful degradation).
- 4Prepare one deep-dive story with specific numbers from past work.
- 5If you've shopped on Flipkart, bring one specific product opinion.
How to master it (over months, not days)
The longer-horizon work. These are the habits that pay off at Senior+ bars where cramming visibly fails.
- Build a product with real users on slow mobile networks.
- Study Flipkart's engineering blog.
- Learn image optimisation, lazy loading, bundle budgets at a working level.
- Make a habit of specific numbers in commits.
- Learn one virtualisation library deeply.
Resources
On-site content for the technical prep, plus short-list of external links worth your time.