
Razorpay Data Analyst interviews reported a two-round process centered on practical SQL, prior-project impact, and product analytics or RCA case reasoning, with basic Python and A/B testing appearing as secondary topics.
$120K
Avg. Base Comp
$154K
Avg. Total Comp
2
Typical Rounds
Not reported
Process Length
Razorpay Data Analyst candidates should prepare first for practical SQL reasoning, rather than syntax recall. One report describes medium-difficulty table-based SQL alongside discussion of previous work; another describes indexing choices, cumulative sums, self-join output, query execution order, joins, and window functions. Be ready to explain the logic behind a query and the trade-offs in an indexing choice, not simply deliver a final statement.
The role-specific discussion can then shift from the query to what the analysis means. Reported questions covered the impact of past projects, presenting the same analysis differently to a Product Manager and leadership, and product-style root-cause-analysis case studies. A candidate also encountered a puzzle, but described deeper case reasoning as the more important part of that conversation. Basic Python, A/B testing, probability, and aptitude appeared in individual reports as supporting topics.
One candidate reported a Hackerearth online assessment with aptitude, probability, combinatorics, and two SQL questions; another reported two rounds beginning directly with SQL and experience discussion. The evidence is limited to two role-adjacent reports, so the assessment should be treated as a possible entry point rather than a universal stage. Build answers around a clear analytical chain: define the business question, query accurately, validate the result, and communicate the decision implication to the intended audience.
Synthesized from 2 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 Razorpay process.
The process moved pretty quickly, which I appreciated at first. I had two rounds total. The first round was a mix of SQL and a conversation about my previous work experience, and the interviewer was actually helpful when I got stuck, nudging me in the right direction instead of just letting me flail. The SQL was around medium difficulty, based on tables, so it wasn’t just syntax recall — I had to think through the logic carefully. The second round felt noticeably more technical and was built around case studies plus a puzzle. That round went deeper into product-style analytics and RCA, and I also got a few basic Python questions mixed in. I answered the puzzle correctly and felt okay about the technical parts overall, but the interviewer seemed to be looking for something more specific in the case discussion.
What stood out most was that the interviewers themselves were nice and experienced, but the process after that was frustrating. I went through all the rounds and then HR just ghosted me, which was disappointing given the reputation of the company. So even though the interviews themselves were fair and the first interviewer was supportive, the communication afterward was poor. If you’re preparing for this role, I’d focus on medium-level SQL on tables, basic Python, and being able to walk through RCA and product case studies clearly under pressure. The puzzle wasn’t the hard part; the deeper case reasoning seemed to matter more.
Prep tip from this candidate
Brush up on medium-difficulty SQL over tables, basic Python, and especially RCA/product case study walkthroughs, since the second round leaned more on that than on the puzzle itself.
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 Razorpay
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Z and t-Tests | |
| Production Rollout Challenges | |
| Reddit-like Notifications | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Experiment Validity | |
| Monthly Customer Report | |
| First Touch Attribution | |
| First to Six | |
| Last Transaction | |
| Top 3 Users | |
| Compute Deviation | |
| Bank Fraud Model | |
| Download Facts | |
| Button AB Test | |
| 500 Cards | |
| Random SQL Sample | |
| Minimum Change | |
| Subscription Overlap | |
| Month Over Month | |
| Prime to N | |
| Paired Products | |
| Upsell Transactions |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reported a Hackerearth assessment worth 90 marks, combining CAT-level aptitude, probability, combinatorics, and two SQL questions. This may be an entry point for some applicants; the report suggests clean SQL performance was important for moving forward.
Candidates report practical SQL questions alongside discussion of their current role and past projects. Topics included medium-difficulty table logic, indexing choices, cumulative sums, self-join output, query execution order, joins, and window functions, plus the impact created by previous work.
One candidate described a deeper round centered on product-style case studies and root-cause analysis, with a puzzle and basic Python questions mixed in. Candidates may also need to explain how they would adapt an analysis or recommendation for a Product Manager versus leadership.