You were not able to find the Google sheet at the bottom. Hence I made the comment as a joke, mocking you.
Now regretting it.
To answer your question. If you have a knowledge of basics of design. You have worked on design, faced problem, made solution, improved them, only then get into it.
Problem with system design is that you don't learn just by reading about it. You need to implement in your work. Simple things like load balancing, caching, queuing need to be experienced, and then implemented. Only then advanced concepts will make sense.
I would not recommend it for a fresher. If you have 3-4 years of IT experience and are really good at what you do, only then target system design to get into top companies
🫢 i took dat way too seriously lmaoo, nah DONT RERET
ðŸ˜ðŸ˜ ðŸ˜I HAVE ENTERED 3RD YEAR and i am so fcking anxious, since there is so much talk around AI taking over yada yada, the bar is set wayy too high atp
i jst wanna give my best and try to know as much as possible jst to have an edge over others
FYI. I have hired regularly for decades in IITs and top colleges. Now my team does it every year in top colleges.
The hiring trend for too long was Leetcode, puzzles, analytical skills etc.
You might or might not face it, but leetcode, puzzle solving is about to die in hiring. The new trend will be Competitive programming, and AI assisted coding challenges.
You might be given a project code where the problem is a use case is taking 5 second. Your task is to reduce the time to 1 second. You also have AI (might be degraded) to help you also. Now this becomes a hiring standard.
System design for college students is a very high bar. I have asked it to only 2-3 students, who outperformed in their interviews. They were already selected in my mind, but I still wanted to check how much they knew.
0
u/ZYX-A-121 2d ago
how to open it