
Flipkart Data Analyst interviews typically combine SQL and Excel testing, sometimes an aptitude screen, and closing behavioral, managerial or HR conversations. Five candidate reports show where to focus your preparation.
$10K
Avg. Base Comp
$16K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Across five candidate reports, SQL is the one skill that comes up every time. Candidates describe joins, COALESCE, ranking with window functions, lead and lag, self-joins, date handling, subqueries and stored procedures. One candidate said the SQL round was labeled easy to medium but moved quickly, and the interviewer wanted the reasoning explained out loud as queries were written.
The rest of the process varies by candidate. Some report an online or aptitude round before the interviews. One described 40 aptitude questions on probability and statistics followed by five medium SQL questions. Another described image and pattern questions added partway through the day. Excel appears in several reports, along with dashboard and visualization questions. Python came up in several reports, and one candidate was also asked about pandas and numpy.
One candidate described a product business case where they had to choose a primary metric, name supporting metrics and discuss tradeoffs. Another walked through an e-commerce dataset focused on customer behavior and churn. If you are preparing, practice turning a vague scenario into a goal, a metric and a recommendation.
The closing stages are described as HR, behavioral or managerial. Candidates mention career goals, past projects and a team conflict, and one said the interviewers followed up on details from the resume. Outcomes were mixed: one candidate accepted an offer and four reported no offer. Total timing was not clearly reported.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Flipkart process.
The SQL round was where I felt most tested, and it set the tone for everything after. It was labeled easy to medium, but the questions moved quickly through joins, COALESCE for handling nulls, and ranking with window functions. I was also asked to explain the difference between UNION and UNION ALL, which sounds trivial until you have to justify which one you'd pick on a large table. I'd recommend practicing these by writing queries from scratch in a plain editor instead of relying on autocomplete, because the interviewer wanted to see how I reasoned through each step.
The business round was a case study. I was given a product scenario and had to decide which metric to track, how I would measure it, and why it mattered for the business. The interviewers weren't looking for a perfect answer so much as a clear structure. I found it helped to state the goal first, pick a primary metric, name a couple of supporting metrics, and then talk through the tradeoffs.
The final round was HR, with fairly standard questions. The conversation also touched on a few basic puzzles and on my resume, including challenges I had faced on past projects and a conflict I had dealt with inside a project team. I'd prepare specific stories for those rather than general answers, since they followed up on details from what I had written.
I received the offer and accepted it. The process was not extremely hard, but the SQL round rewarded candidates who could explain their logic clearly as they wrote.
Prep tip from this candidate
Drill window functions, joins, COALESCE, and the UNION versus UNION ALL distinction, and be ready to explain your query logic out loud. For the business case, state the goal and define the primary metric before you discuss anything else.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Flipkart
How would you assess if a coin is fair after observing 8 tails in 10 flips?
| Question | |
|---|---|
| Max Quantity | |
| Bagging vs Boosting | |
| Same Side Probability | |
| HHT or HTT | |
| Jars and Coins | |
| Dijkstra implementation | |
| Hurdles In Data Projects | |
| Biased five out of six | |
| Count Transactions | |
| Merchant Dashboard Design | |
| Flipping 576 Times | |
| Underpricing Algorithm | |
| Bias vs. Variance Tradeoff | |
| Biased Random Number Generator | |
| Possibly Biased Coin | |
| Seller Type Modeling | |
| All Tails Consecutive | |
| Why Do You Want to Work With Us | |
| Evaluating Revenue Decline | |
| Bag of Different Coins | |
| Bias Variance Tradeoff | |
| Meta in an Emerging Market | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Customer Orders | |
| Longest Streak Users | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One went through a resume screening round after applying through Naukri. Others had a short phone or talent acquisition call about background and experience. It is typically a fit check, so prepare a concise summary of your analytics work.
Some candidates report an assessment before the interviews. One described 40 aptitude questions on probability and statistics plus five medium SQL questions. Another met an aptitude round of image and pattern problems that was added unexpectedly. Others did not mention one, so it may vary by hiring cycle.
Candidates report joins, COALESCE, UNION versus UNION ALL, ranking and window functions such as lead and lag, self-joins, date handling, subqueries and stored procedures. Excel formulas, statistics, dashboards and basic Python or pandas also appeared for some candidates. Expect to explain your logic while you work.
One candidate received a product case and had to choose a primary metric, supporting metrics and tradeoffs. Another analyzed an e-commerce dataset for customer behavior and churn trends. These reports suggest interviewers may value structured reasoning and business relevance as much as the answer.
Candidates describe a closing round covering motivation, career goals, past projects, team conflict and cultural fit. Some describe it as managerial and others as HR. One candidate was asked a few basic puzzles and follow-ups on resume details, so prepare specific project stories.