Candidates who clear Razorpay loops consistently describe having concrete, ready-to-discuss designs for common backend systems rather than improvising from a blank page — prepare DSA, LLD, and behavioral/culture-fit as separate tracks.
A track-by-track roadmap
DSA: Razorpay assessments lean on graphs/shortest-path, binary-search-on-answer, and knapsack-style DP more than pure brute-force problems. Work through the DSA Interview Questions here, and revisit core data-structure fundamentals — a strong SQL foundation matters too for backend-heavy roles.
LLD: Practice going from a vague prompt (e.g. "design a logger") to requirements to class design out loud — Razorpay interviewers often give intentionally underspecified prompts on purpose, then push into how the design behaves at scale across multiple instances. Start with the LLD Interview Questions here.
Machine coding & system design: Expect to actually build (not just whiteboard) components like a load balancer or search engine, and to design real services like job schedulers and notification systems — structure every design answer the same way: requirements, API design, data model, then failure handling.
Behavioral & culture-fit: Prepare 2–3 real stories that can each answer multiple questions, in STAR format. See Behavioral & Culture-Fit Questions.
A recurring piece of advice across candidate reports: move through the basic CRUD/data-model part of a design round quickly so there's real time left for caching, database trade-offs, and failure-scenario follow-ups — that's usually where interviewers dig deepest.
Read real, round-by-round Razorpay Interview Experiences to see how this plays out in an actual loop.