Classic mistakes! Especially that first one I mentioned 👀

“Not leveraging your recruiter” hits HOME for me. That one is so underrated because your recruiter can truly be your biggest advocate .. and they can honestly help you become WAY more prepared for interviews if you just ask. Asking for more resources, more information, informational sessions with other engineers etc. can be vital at the end of the day. Great video, as always!

Video on Clement's channel: kzfaq.info/get/bejne/gZtoqZegus2qlmQ.html

That was a smooth plug 😂

Needless to say, these can be applied to any job interview in corporate America, not just for tech jobs

GREAT tips, great duo, thanks guys 😄

Am I not happy to see you two together again?? Damn sure I am!

I can see clem reflecting on the second mistake 😂 I believe he learned python in a week or so to go through the whiteboard interview. great to see both of you collab again

Raul face in thumbnail was superb

Can you make a video talking about how you think about the future development process? ( the way developers will develop, tools, programming language, interview process, etc).. Like next 10 years, next 20,50,100 years

Can we have the next video on "Top mistakes recruiters/hiring managers make"?

I'm working as an SDE, but in the end everyone wants to be a part of MAANG, it is the best for me. Thanks a lot

Can you kindly have some suggestions on getting an interview - things to do and put in the resume to get it selected, how to apply, etc..Thank You very much!!!🙏

new subscribe from element's channel!

Thanks for stopping me using Java instead of my main skilled tool JS 😀 Great information as usual 🙏

@Rahul Pandey, I am actually surprised that neither of you mentioned this, by in my opinion, I think the most common mistake by far is trying to route memorize the actual solution for problems. In the initial phases of my prep, I tried to do this and got destroyed. So I recommend people NOT to do this and try to really understand the algorithm itself and how to modify it according to the problem at hand.

Question: are OOP questions asked during the system design section of the interview?

What about the revision part of dsa ? How to revise data structures

The bold points u added on screen... Could u do tht thing at the bottom cuz tht would've looked much better... Btw thanks fr the video. :)

It was a joke bro. I love u

Half of the recruiters I’ve met are SO bad at their jobs. Randomly cancel meetings, don’t respond to emails, or give straight up incorrect information. The what’s helpful to study or types of interviews should just be in an email. Almost every company has the same 1 hr coderpad phone screen the 4 hour on-site after that structure anyway

hey rahul how much mathematics is required for computer science ?

Hi Rahul, I must say this you strongly resemble Sonu Sood in your looks.

Imagine having to prepare for weeks just for an interview. Pass

The 7th biggest mistake is to watch videos by Clement the pineapple.

Can't really agree with Mistake 2. Spend sometime to get accustomed to python or maybe js / go if you prefer and use that imo. You are ultimately just writing loops and ifs. No fancy syntax needed. No need to get too in depth into language specifics like list comprehensions and such. Choosing languages like c# java c++ on a whiteboard is just not a good idea. Say you want a map in python. my_map = {} Done. Try this in Java. Not just the amount of syntax. Which map? HashMap? TreeMap? LinkedHashMap? How about a list in Java. Use array or ArrayList? Or even LinkedList if it comes to it. You now also need to consider if you expecting the size to grow or not and decide the proper DS. How about a String? Try looping a String in Java and compare that to looping a String in Python. You need to make considerations you simply won't bother with in Python when you use static typed languages. Don't get me wrong. I use Java and bits of C++ in everyday work and am a fan of Java particularly. But they are just not whiteboard coding material.

I will be blunt with feedback: this feels like a 10 minutes ad for algoexpert with some plain out wrong ideas (Pareto's principle: why would you over-prepare when your time is limited and preparing on something you're already strong in will give you diminishing returns compared to stuff which you don't know as well?) and other common sense/always repeated stuff like the "explain your logic out loud" (which is literally such a common idea it is included in google's preparatory video for interviews). The quality of this video compared to other videos on this channel is really low.

lol can someone list all the mistakes ? I don't wanna go through the whole video.