Amit Bhardwaj

I have researched lots of product-based companies like Amazon, Microsoft, Netflix, Zomato, Goldman Sachs, Paytm, J.P. Morgan etc., for SDE1 2 roles, and found that these 20 system design questions are almost asked in every interviews, both at the fresher and experienced levels. 𝐅𝐫𝐞𝐬𝐡𝐞𝐫 𝐋𝐞𝐯𝐞𝐥 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 1. Design a simple URL shortening service. 2. Design a basic chat application. 3. Design a file storage system. 4. Design a simple social media platform. 5. Design a simple search engine. 6. Design a simple e-commerce website. 7. Design a basic ride-sharing system. 8. Design a basic video streaming service. 9. Design a simple recommendation system. 10. Design a basic food delivery app. 11. Design a parking lot management system. 12. Design a simple music streaming service. 13. Design a basic online ticket booking system. 14. Design a simple note-taking application. 15. Design a weather forecasting system. 16. Design a basic email service. 17. Design a file synchronization system. 18. Design a simple calendar application. 19. Design a basic online quiz platform. 20. Design a user authentication system. 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞𝐝 𝐋𝐞𝐯𝐞𝐥 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 1. Design a URL shortening service like bit.ly. 2. Design a distributed key-value store like Redis. 3. Design a scalable social network like Facebook. 4. Design a scalable recommendation system like Netflix. 5. Design a distributed file system like Hadoop's HDFS. 6. Design a real-time messaging system like WhatsApp. 7. Design a web crawler like Google. 8. Design a distributed cache like Memcached. 9. Design a content delivery network (CDN) like Cloudflare. 10. Design a scalable search engine like Google. 11. Design a ride-sharing system like Uber. 12. Design a video streaming service like YouTube. 13. Design an online food delivery system like Zomato. 14. Design a collaborative document editing system like Google Docs. 15. Design an e-commerce platform like Amazon. 16. Design a recommendation system for an online marketplace. 17. Design a fault-tolerant distributed database system. 18. Design a scalable event-driven system like Twitter. 19. Design a scalable photo-sharing platform like Instagram. 20. Design a distributed task scheduling system. Learn and solve these, and you’ll be fully prepared for your next System Design interviews.. System design can be tough to crack, but having the right resources makes all the difference. Came across this well-structured, in-depth guide definitely worth a read. 𝗖𝗵𝗲𝗰𝗸 𝗶𝘁 𝗼𝘂𝘁 𝗵𝗲𝗿𝗲: https://lnkd.in/gxRRyd2m #tech #collab

4,818

158 Comments

Here are 3 Lessons I’ve learned in my 3 yrs as an SDE that changed my life. LESSON #1 → Asking early saves you time later. Whenever I got stuck, I reached out, paired with a teammate, shared logs, or walked through the flow together. A good engineer doesn’t solve problems alone, they solve it faster with collaboration. LESSON #2 → Take feedback seriously. Whether it was Code or design reviews, the feedback stung at first, but acting on it made me sharper. Each review wasn’t about “fixing mistakes” but about raising my bar. LESSON #3 → Systems break at the edges. The happy path is easy. What I started focusing on were edge cases: timeouts, retries, failover behavior, scaling limits. That attention to detail made me more confident in production environments. Working at Microsoft & now Salesforce, these lessons have shaped me into more than just an engineer who codes & into someone who owns systems end-to-end. So if you’re a working SDE preparing for your next switch to mid-level SDE roles while working full-time, I’d strongly recommend Bosscoder Academy. 🔗 Explore their programs here: https://bit.ly/4gBc1Il They’ve already helped 2200+ engineers land roles in top PBCs with structured prep in DSA, System Design, and Full Stack, 1:1 mentorship, mock interviews, resume support, and 100% job switch guidance. #sdeprep #career #jobswitch #systemdesign #growth #collab

284

7 Comments

A few years ago, a Senior SDE I connected with on LinkedIn told me → “The higher you go in your career, the more you’ll feel burnt out unless you create a work-life balance.” I didn’t take it seriously then. But after 8 yrs in tech, esp. while leading teams at S&P Global, I felt it too, only, I realised it too late. Burnout doesn’t come crashing in one day. It creeps up slowly. You start losing excitement for work. You feel distracted, tired, but still show up every day because that’s what you do. I was still delivering, still writing code, making sure things shipped on time, but deep down, it didn’t feel right. What have I learned since?  → Leadership at senior roles is not just about solving bigger problems, it’s about managing yourself, your energy, and your perspective. If you ignore that, burnout will take away the joy of what you worked so hard to achieve. If you’re a mid-to-senior level engineer looking to step into leadership roles or accelerate your growth without burning out, structured guidance can make a huge difference. That’s exactly what Bosscoder Academy’s EVOLVE Program offers to SDEs with 6+ YOE, explore it here 👉 https://bit.ly/41lqhhY They’ve already helped 2200+ engineers crack top product-based roles with a well-structured curriculum for DSA, SD, and full-stack development, 1:1 mentorship from industry experts, and 100% job switch support. #leadership #tech #burnout #seniorsde #worklifebalance #collab #jobswitch

145

27 Comments

This was the FIRST LLD question I got in 2 out of 3 interviews. And I messed it up 🫤 The question seemed harmless “Design a leave approval system.” I jumped into code. Nested if-else. Done. ✅ 🤣 But then came the follow-up- ➤ “What if I want to add another approver?” ➤ “What if Director is on leave?” ➤ “Can you make it scalable and clean?” That’s when I blanked 😭 Here’s what I wish I knew back then- The interviewer was looking for Chain of Responsibility, not hardcoded logic. Think of it like a relay race. 💡 This one pattern teaches: • Clean code separation • Extensibility for real-world needs • Reusability across different systems Whether you're prepping for system design or writing backend logic—this pattern is gold. Especially when you want your code to grow with your product. Dive into a full breakdown (with Java code)-> https://lnkd.in/gPPQzybF

154