Backend engineer at Razorpay, working on payment systems in Go. Things that handle millions of requests a day.

github

Bhavesh Garg • Peerlist

LeetCode tells you you're wrong in 2 seconds. System design lets you find out in the interview.<a target="_blank" rel="noopener noreferrer nofollow ugc" class="break-all link-break text-gray-500 hover:underline" href="https://algosd.fun">algoSD</a> fixes that. Drag in load balancers, app servers, caches, databases, queues, and CDNs. Wire them together and hit simulate. Traffic flows through your design, and anything that can't keep up turns red.Then an AI interviewer reads what you actually drew and asks the follow-ups a real interviewer would: "Your DB is at 140% load. What now?" or "What happens when this cache goes down?"<ul><li>35+ problems, from URL shortener to Uber and Netflix</li><li>Reference design for every problem to compare against</li><li>Scored on scalability, availability, latency, cost, and trade-offs</li><li>Free, no signup, runs in the browser</li></ul>Built it because system design prep has no feedback loop. Would love to hear what breaks, in your design or in mine.