Meesho Data Analyst Interview Guide

The process was fairly straightforward, but it was much more SQL- and case-focused than a general behavioral interview. I first completed a SQL test, followed by two interview rounds. Both interview rounds included case studies, while SQL knowledge continued to come up throughout the process. The interviewers checked fundamentals directly, including what a CTE is and how it differs from a subquery, but the questioning could also become considerably more technical. I had to work with window functions and partitions, including window-frame concepts such as RANGE. Joins were another important area: I was asked about different join types and had to write out the expected output for each one rather than merely explain their definitions.

The case portions centered on data interpretation and root-cause analysis. I was given scenarios, asked to identify the important signals in the available information, and then expected to propose a logical explanation or solution. These questions felt less like puzzles with one fixed answer and more like tests of whether I could structure an ambiguous business problem and defend my reasoning. There was also some conversational discussion about my introduction, academics, college experience, and projects, along with the motivation question of why I wanted the Data Analyst role. The interaction itself was smooth and relaxed, even when the SQL questions became difficult.

Overall, I found the process simple in structure but uneven in difficulty: basic SQL definitions appeared alongside hard questions on window functions and exact join outputs. I ultimately received an offer but declined it. My main takeaway is not to overlook SQL fundamentals, because the interview can move quickly from definitions into writing queries and manually reasoning through their results. For the cases, I would practice explaining how I isolate a root cause from data instead of jumping immediately to a conclusion.