Would be nice to have a small tutorial about the network protocols. It will help those who didn't have computer network in their curriculum but they ended up in IT. To be honest it's a very huge subject to tackle.
The part about unneeded capacity estimation resonates. I gave one of those in a recent interview, and while it didn't ruin the interview for me, my interviewer made it pretty clear he wasn't interested in hearing these numbers and wanted to move on.
Great points... Just one suggestion.. can you please make videos on the protocols we need to be aware of as Senior developers.. and the internals/handshake we need to know
1.don't have a set introduction 2.don't do capacity estimation without any reason 3.for Sr., focus on network protocol Sys Des interview is NOT about building a working sys but measuring your aptitude 4.understand the internals of systems 5.think of trade-offs bonus. stay with the problem
Dude before u even start designing, always ask the questions "what r v going to solve/ achieve here". This understanding is the main thing that I'm looking forward to c from any candidate when I'm doing any interview. Good content N keep coming.
Gaurav and Narendra (Tech Dummies) have taught me so much. They teach every concept and every detail with such patience and finesse. Thank you so much Gaurav
It is amazing to see how many youtube videos talk about what component does what but barely anyone talks about what is expected of candidate in an interview. Because we see so many of these vidoes on how to build this and that, when you face the question in real interview, you are just thinking of what to throw at interviewer thinking that that's going to work but in reality its only making your interviewer think that you just read that somewhere. I couldn't agree more with envelop estimates. Now see all these youtube videos and almost every single one of them has 5-10 mins spent on that. What's the conclusion of all these estimates??? For the most part nothing. We were going to do the same without it anyway. The main point to take away here is to keep in mind to stay focus on the problem given. Setup the stage quickly (Functional/ Non-Functional requirements and main entitles for the system and Rest API calls if the product is client facing) and then do a quick High level diagram. Then its time to stay focused on the question and talk about the trade offs in deep dive. That's what I have gathered so far after spending tons of hours and some mocking interviews. Hoep this helps out others to stop wasting time into other things. Put simply, if you do everything right but didn't spend time on the core of the problem, you failed.
TCP and UDP are the transport layer protocols where TCP backs application layer protocols like HTTP, FTP, etc...just wanted yo know what other protocols are u meaning when you say it
Hi Gaurav, so for capacity panning, are you saying we don't have to bring it up unless interviewer specifically asks? You said talk about it if the system is not scalable or may collapse, but how would you know that before hand if no user requirements have been defined. Anything will collapse with too many users :D
These kind og System design interviews are more about showoff. Just learn about load balancer, autoscalling, microservice, kafka, logging service, databse replica draw some stupid diagrams and u can crack it. I personally feel like it should be more about database design, choosing the right set of technology, api security, architecture of ur code. Choosing between different databse system.
Amazing video bhaiya, one thing i want to ask..... does your course contains LLD as well as HLD in detail ? And you are adding more videos in that course in same subscription right ??
How many of these mistakes are also applicable for a *new grad* SD interview?? For eg, I dont know anything about the different network protocols, or the pros and cons of specific DB products (like Cassandra or Elastic). Will leaving out the examples fine in this case?
Off topic, but if possible can you please take a video on Top K trending (per hour, per day, per week), where we need to handle the case of removing old views/likes.
Great videos! Could you make videos focused just if system design and not for interviews? I ask this because I'm trying to structure my first project and it's so hard.
actually when you spoke about Network Protocol, the first thing that came to my mind is the definition of Microservices Architecture - a Protocol aware heterogeneous interoperable architecture!!
Bro that's (1:36) exactly what happened with me y'day. I had an interview at a Top Hotel Management company. The First round was DS and Algo, I cracked it next round was of SD. I failed miserably because I can't answer how'll the services communicate with each other. >.< I fucked the interview. I know the result but I'm hoping for good because I'll learn a lot there.
I will share my experience. Question was on Book my show. Btw she gave me option for irctc and book my show. I should have chosen irctc😂 I actually expected interviewer to tell me to go for architecture designing. Discussed features, then database design after getting instructions and she was telling me to just write down design and then we will discuss. I was clearly not expecting something like that. N my mistake was to stop at db design i should have just said can i go ahead with system architecture. Interviewer just dived into storing seating arrangement with spaces in between for db design. N was not convinced with my approaches for this particular thing😛 1 hour was wasted on this n i got rejected
Would be nice to have a small tutorial about the network protocols. It will help those who didn't have computer network in their curriculum but they ended up in IT.
To be honest it's a very huge subject to tackle.
Was about to ask same. Very well explained but would help if we had a brief video on Network protocols
The part about unneeded capacity estimation resonates. I gave one of those in a recent interview, and while it didn't ruin the interview for me, my interviewer made it pretty clear he wasn't interested in hearing these numbers and wanted to move on.
Great points...
Just one suggestion.. can you please make videos on the protocols we need to be aware of as Senior developers.. and the internals/handshake we need to know
I'm working on it :D
@@gkcs Waiting on this man..!
I am a simple man, I see a GKCS video, I like it. Was about to go to sleep, saw the notification and I am glad I saw the video.
That was one hell of a humorous introduction! 🤣🤣🤣🤣
100% making sense. I guess this video is really helpful for senior developers. Echo to all those points. And great content. Keep it up!❤❤❤
Great Tips ! Your Content always adds something new to my set of knowledge !
1.don't have a set introduction
2.don't do capacity estimation without any reason
3.for Sr., focus on network protocol
Sys Des interview is NOT about building a working sys but measuring your aptitude
4.understand the internals of systems
5.think of trade-offs
bonus. stay with the problem
Dude before u even start designing, always ask the questions "what r v going to solve/ achieve here". This understanding is the main thing that I'm looking forward to c from any candidate when I'm doing any interview. Good content N keep coming.
Great points!
Thanks.
Great as always!!!1👍👍
One of your Best Intro 😂🤙
Great content. Video quality has improved a lot, congrats and thank you for sharing.
Great content! Love your videos, they're always super helpful.
Great video Gaurav Sen, thank you for sharing!
Very useful, Thanks Gaurav for sharing.
your video intro is unique and best everytime
I realized i made 3 of these mistakes in a recent onsite... smh... thanks Gaurav, I now understand why I didn't get that job.
Point to Point, thanks for this.
Great lessons. Thanks!
Very informative GKCS! Kudos!!!
Will make sure to follow this in my next interview 😉
That saas bahu clip 😂 & amazing tip
Thanks alot for making it easy !
Thanks a heap, mate .
Great tips!
Gaurav and Narendra (Tech Dummies) have taught me so much. They teach every concept and every detail with such patience and finesse. Thank you so much Gaurav
Binge watching videos on this Channel❤️
excellent presentation
Thank you!
It is amazing to see how many youtube videos talk about what component does what but barely anyone talks about what is expected of candidate in an interview. Because we see so many of these vidoes on how to build this and that, when you face the question in real interview, you are just thinking of what to throw at interviewer thinking that that's going to work but in reality its only making your interviewer think that you just read that somewhere. I couldn't agree more with envelop estimates. Now see all these youtube videos and almost every single one of them has 5-10 mins spent on that. What's the conclusion of all these estimates??? For the most part nothing. We were going to do the same without it anyway.
The main point to take away here is to keep in mind to stay focus on the problem given. Setup the stage quickly (Functional/ Non-Functional requirements and main entitles for the system and Rest API calls if the product is client facing) and then do a quick High level diagram. Then its time to stay focused on the question and talk about the trade offs in deep dive. That's what I have gathered so far after spending tons of hours and some mocking interviews. Hoep this helps out others to stop wasting time into other things. Put simply, if you do everything right but didn't spend time on the core of the problem, you failed.
Would be great to have a video on different network protocols (other than common ones like HTTP, FTP, TCP, UDP) :P or some resources around it
TCP and UDP are the transport layer protocols where TCP backs application layer protocols like HTTP, FTP, etc...just wanted yo know what other protocols are u meaning when you say it
Thank you
Hi Gaurav, so for capacity panning, are you saying we don't have to bring it up unless interviewer specifically asks? You said talk about it if the system is not scalable or may collapse, but how would you know that before hand if no user requirements have been defined. Anything will collapse with too many users :D
Hi Gaurav, very nice video, presentation has greatly improved.
What do you think about DDIA for system design?
These kind og System design interviews are more about showoff. Just learn about load balancer, autoscalling, microservice, kafka, logging service, databse replica draw some stupid diagrams and u can crack it.
I personally feel like it should be more about database design, choosing the right set of technology, api security, architecture of ur code. Choosing between different databse system.
Thanks for the videos. They are short and pretty helpful. Is there a video for CAP theorem?
It's really great...
Love it. Need I say more?
Omg that intro was 🔥😂
Great!
gRPC is not a network protocol right? we can not compare it with HTTP
Do u have any series on network protocols?
Amazing video bhaiya, one thing i want to ask..... does your course contains LLD as well as HLD in detail ? And you are adding more videos in that course in same subscription right ??
Yes it does. The upcoming videos for this course will be added free of cost to existing users.
@@gkcs ok great, LLD and HLD is there in course right ?
@@roushanraj8530 Yes there's 3 chapters on LLD and 5 on HLD.
Can you make a video on ' How to Design Web Servers
How to use asynchronous messaging for user registration or order saving payment deduction etc where instant response needed.
Still laughing at the intro :D
How many of these mistakes are also applicable for a *new grad* SD interview??
For eg, I dont know anything about the different network protocols, or the pros and cons of specific DB products (like Cassandra or Elastic). Will leaving out the examples fine in this case?
Youjer got me :)))
Off topic, but if possible can you please take a video on Top K trending (per hour, per day, per week), where we need to handle the case of removing old views/likes.
Great videos!
Could you make videos focused just if system design and not for interviews?
I ask this because I'm trying to structure my first project and it's so hard.
Sir urgent need for system desing video on Google analytics. Please
Hi, does interview ready have sections on internals of various DB options and about network protocols?
The design discussions include DB and network tradeoffs when needed.
Hello Gaurav sir, I am still in college and will be graduating next year. How much do you think I should focus on systems design as a fresher?
low level design only
actually when you spoke about Network Protocol, the first thing that came to my mind is the definition of Microservices Architecture - a Protocol aware heterogeneous interoperable architecture!!
Hey! Does anyone know what is a good resource to learn the protocols used by internal systems to communicate with each other?
Tips are good. But you are specking too fast. Please reduce your pace 40%. Thanks
I'd suggest going to video settings and changing the playback speed to 0.5 😛
@@gkcs then it will become a slow motion... 😃
Bro that's (1:36) exactly what happened with me y'day. I had an interview at a Top Hotel Management company. The First round was DS and Algo, I cracked it next round was of SD. I failed miserably because I can't answer how'll the services communicate with each other.
>.<
I fucked the interview. I know the result but I'm hoping for good because I'll learn a lot there.
Hard luck, but all the best for the next interview 😁
I will share my experience.
Question was on Book my show.
Btw she gave me option for irctc and book my show. I should have chosen irctc😂
I actually expected interviewer to tell me to go for architecture designing. Discussed features, then database design after getting instructions and she was telling me to just write down design and then we will discuss. I was clearly not expecting something like that.
N my mistake was to stop at db design i should have just said can i go ahead with system architecture.
Interviewer just dived into storing seating arrangement with spaces in between for db design. N was not convinced with my approaches for this particular thing😛
1 hour was wasted on this n i got rejected
Thank you for sharing this ⭐
@@gkcs it was my first design interview. I hope because of ur vids i can clear next ones👍🏻👍🏻
Oh bhaisahab 🤣🤣🤣🤣inteo
point 6: dont have an indian accent because the interviewer wont understand shit
Preparing for a system design interview? Head to get.interviewready.io!
Wishing you a great day ahead!
Lmao the intro
Haha