1. what i did wrong 2. adopting a long term mindset 3. study a little bit every day 4. quality over quantity 5. practice mock interviews 6.approach topic in logical order
@@kannannatarajan9398 I was skipping around the video and at the end of one of the points he made, he says we should follow the link below or something.
Don't memorize questions, just understand every concept and every detail about the language. Also recommend learning to convert your code to binary on the fly using nothing but 2 rocks and a pencil.
I wish I would have found something similar to this video earlier Ive been struggling for the past year and 2 months after graduating to find an entry level position. But after doing a bunch of interviews Ive learned all these things the hard way. I work fulltime currently to pay bills so i figured practicing and memorizing solutions was good enough but after reaching the final interviews a few times and seeing that the foundation is what really matters ive changed my study habbits. Currently I am doing an interview at this big tech company so wish me luck guys! And thanks Kevin really love your content
awesome video. PLease do a roadmap video explaining the approach topics in logical order. I bet there are hundreds of people needing that wide explanation.
I am in my 2nd year of CS. I have just completed my Data Structures course. I have started applying for tech internships. I have already sent out so many applications. I guess it has to do with my resume because I can't even get interviews. Also there is a recession going on in tech, so I have to fight an uphill battle too. But I know I just have to keep applying.
Great advice! I have a long history of struggling with interviews and I have recently begun to adopt most of your advice (I have yet to invest proper time practising mock interviews but I will). Wish I had this mindset back when I was your age! Never too late, I suppose!
Very practical and helpful. I’m already in the pipeline with a couple companies, and I’m realizing just how many problems there are out there, in addition to the soft skill polishing. This is encouraging, however, and makes sense to me in my experience.
Hey Kevin, I'm a big fan of your channel. I failed in google interview recently. I'm learning from my mistake. I'm working on it. Thanks for posting this video. I'm preparing for the interview and planning to give interview in few months. Definitely I'll get selected in my second attempt. After joining google, I will ping you through the internal messenger to say "Thank you "
I kind of disagree with the numbers thing, solving as many problems as you can isn't bad as long as you do it for the right reasons, and the best reason for doing so is to improve your problem solving skills, part of this "game" is to also train yourself on how to Respond to a problem you haven't seen before, and the best way to do that is... of course, Is to solve as many problems as you can. Also, I have seen at least a couple of cases of "slow learners" who made it to Google, FB, etc (on their 2nd, 3rd attempt)... and their common denominator was their problem count (over 1000 problems). Anyways, just my humble opinion.
Thanks for saying this:) Your comment gives me so much hope. I’m a career transitioner/slow learner and hope to crack my Google interviews in 3 months by solving 1000 plus Leetcode questions.
@@superniftysuzy1 Not sure if you were being sarcastic? but if you weren't, 1000 problems in 3 months sounds like you'll need a 12 hours/day schedule to get it done.
can you talk about how to prepare for system design interviews? There are tons of resources on coding interview preparation, but quality information on system design interviews are far and between.
to me every System design is different but interestingly all of them have only one solution ! So many don't agree but it's the truth ! In an interview think how many system design interview you go through that speaks for itself !!
I've heard that System design interview book from Alex Wu.... is a must read. Despite the fact that I've never ever read it. There is a repo on GitHub called system design primer, that is very good too. but I hope it could help you starting to figure out how to improve your studies on design system.
Guarav Sen’s system design playlist on RU-vid is incredible. If you have money educative’s web applications and architecture 101 course/grokking the system design interview are great too. The 101 is a great introduction and grokking is just practicing what you learned.
1. read examples and solutions to typical questions 2. if you can’t adapt a problem you’ve seen in the past, rely on an architecture you’re most familiar with i recommend learning the key points for a few areas (ie kubernetes distributed via containers on the cloud or something) advocate for your points hard. state it’s advantages, but suggest alternatives often! in the end you should still confidently propose your idea. so you have a flow chart of have i seen this or anything similar? (9.5/10 you will) if not you rely on architecture you’re familiar with as the answer, while suggesting alternatives. I also recommend using UML and Objects to demonstrate you’re thinking in an object oriented manner in either scenario.
Honestly, great advice. I had similar intuition when starting. I tackled a decent amount of easy problems before moving onto mediums. It is important to build a solid foundation. Also, the 2-3 per day and mock interviews sounds spot on!
This is a crazy example on how little universities prepares you for Software Engineering Jobs. How can you not be able to solve Medium Leet Code questions after 3-4 years of CS.
Thank you, Kevin, you have been my motivation in my interview prep! Really important advice here, man! I was guilty of the same 'memorization' approach until I realized it was not gonna cut it. Big question: it is believed that FAANG companies are language agnostic, nevertheless, how come when it comes to resume projects most tech bloggers recommend doing React projects? What if a person has been learning some other lang./framework? What would be your advice for self-taught developers regarding the most optimal lang./framework/stack for an entry level job in top tech companies?
Based on what I've read so far, it would be more impressive for the interviewer to have something to look at and be able to visualize what you did rather than have a console print out some numbers which may have some complex logic behind them, but is not as memorable. Clement Mihailescu has a video regarding this, pretty useful, you should check it out. Also, if you really wanna get in big tech, you can always use linkedin to look up employees from the company you're trying to land a job at and politely ask for tips. A high chance someone might actually help you out
Why are we not mentioning the more important interview rounds: sys design and behavioral? Lc is a minor portion of the interviewing process, design is what matters most.
I’m stuck between trying to learn tech like node, react or sql and ONLY studying for coding technical interviews. I have more fun learning new things like things we do typically on the job rather than technical interviews. I guess I have no choice right now to buckle down and study for tech interview first before learning on the job stuff. What do you guys recommend?
@@moezzzz9341 Salaam! That's not a bad idea. I will try this out. Maybe after work I can do 1-1.5hrs on tech interviews then 1-1.5hrs with learning new things
Hey Kevin, do you recommend learning a new language specifically for leetcode? I currently know C++ but I see a ton of people recommend learning python for interviews.
I think C++ is a good option if you're comfortable with it. It's one of the more popular languages used for coding interviews so no need to learn a new one
Can't you just use pseudocode in interviews? If you want to get a position where you will write in C++ it doesn't make any sense to use python for interviews
What if you have a small baby and can’t spend time on studying problems? Then what? Isn’t this process unfair toward people who have families? Shouldn’t your experience count for something?
Hi Kevin! I keep forgetting leetcode concepts and tricks. I do not mean that I memorise a problem. But I do want to know if you used spaced repetition?
Hey Kevin, I have been following your channel for quite some time now. I have learned a lot. Just one suggestion, If you can explain the algorithm by dry running it with an example, would help us visiualize it better. Thanks, Your Subscriber
I struggle a little bit when people say "don't memorize the solutions." When you're starting out, or really, whenever you're stuck, how do you make progress on the problem? Isn't it better to spend 30 mins learning something than spending those 30 mins just being stuck?
Not memorizing solutions doesn't mean to not look at how other people have solved this. It means to not just cram it and understand why the solution is working. When you do this, you will be able to apply same strategy to other problems as well.
You should definitely look at solution and learn from it but not copying it exactly. Try to understand the solution and put it away then code it yourself. It is even better if you just read the explanation (not the solution code) and create your own code from that.
Interviewer means the person asks question in a job. Interviewee means the person answering questions. As an American and a engineer you should command these words before creating a video about interviews. Meant as a harmless feedback. No harm intended 😃.
