Low-Level Design rounds at Razorpay ask you to model a real backend component end to end — a logger, a message broker, an ATM — starting from requirement clarification, not a pre-agreed class diagram. Interviewers expect you to justify any design pattern you reach for rather than just naming one.
Problem 1Design a Configurable Logging System
Design a logging system that supports multiple severity labels (e.g. info, warning, error) and routes each log entry to a different destination — console, file, or a web endpoint — based on configuration read at startup.
- Clarify requirements yourself first: what severity labels must be supported, and can a single log entry fan out to more than one destination?
- Think about how new destinations (e.g. a future Slack or webhook appender) could be added without modifying existing logging call-sites.
- Be ready to justify any design pattern you reach for, not just name it.
More verified Razorpay LLD prompts will be added here as additional candidate reports are reviewed and confirmed.