6 Mistakes To Avoid When Preparing for Your FAANG Interview

[@clem]

Classic mistakes! Especially that first one I mentioned 👀

[@hammad8965]

OMG 😂 first mistake lol

[@milesroyer172]

It was pretty good Clement :)

[@deathbombs]

Bigger mistake is not using leetcode lol

[@PoojaDutt]

“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!

[@RahulPandeyrkp]

Thanks Pooja!

[@element720]

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

[@adityakumar3346]

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

[@elliott614]

MAANA*** google is actually alphabet now

[@codinginflow]

That was a smooth plug 😂

[@algorithmsillustrator3313]

@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.

[@foreverYogiii]

imo you should memorize problem patterns and then apply them to whatever the problem is. if you do enough problems the memorization part comes naturally

[@algorithmsillustrator3313]

@@foreverYogiii yup couldn't agree more.

[@RahulPandeyrkp]

good point, Alex and I talked about not memorizing the solution in the session about DSA interview prep (videos available in the app)

[@universecode1101]

GREAT tips, great duo, thanks guys 😄

[@RahulPandeyrkp]

💯💯

[@envyos814]

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

[@GaganKPolska]

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

[@RahulPandeyrkp]

good idea!

[@abh9789]

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!!!🙏

[@RahulPandeyrkp]

Please check out the mobile apps (link in description), we cover this :)

[@alexascensao8024]

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

[@RahulPandeyrkp]

They could be -- often you're demonstrate your OOP knowledge in the context of explaining how you'd design a program

[@malikau917]

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

[@peeranpc4262]

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

[@ericgeppert4252]

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

[@RahulPandeyrkp]

I've had mixed experiences with recruiters as well. It helps to ask questions to try to gauge how familiar they are with the company.

[@vishalmane3139]

Raul face in thumbnail was superb

[@hoyinli7462]

new subscribe from element's channel!

[@RahulPandeyrkp]

welcome!

[@nishantgiri919]

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. :)

[@RahulPandeyrkp]

good point

[@DC-yw5yg]

It was a joke bro. I love u

[@madetolaugh3476]

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

[@RahulPandeyrkp]

This one was about mistakes, we cover some the revision parts of DSA in our mobile app

[@syediftekharuddin3769]

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

[@RahulPandeyrkp]

he's probably much, much stronger than me 😂

[@ANUJKUMAR-wc9dz]

hey rahul how much mathematics is required for computer science ?

[@RahulPandeyrkp]

Depends on the field of comp sci, but for most software engineers, very little math is required

[@ANUJKUMAR-wc9dz]

@@RahulPandeyrkp so there is no need to get in depth of calculus, statistics and probability

[@tamilshoutcom]

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.

[@RahulPandeyrkp]

if you have enough time to properly pick up the language (and not just a few weeks *only* writing leetcode for it, I think what you're saying makes sense!

[@semicolon101]

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

[@RahulPandeyrkp]

Video on Clement's channel: kzbin.info/www/bejne/gWabp2elisx5nJI

[@Rppiano]

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

[@ChaosB7ack]

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.

[@RahulPandeyrkp]

I appreciate the feedback, collabs are tricky. I do see how the algoexpert plugs may be distracting.

[@manisharyal4239]

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

[@RahulPandeyrkp]

www.linkedin.com/posts/rpandey1234_chatted-with-clement-mihailescu-about-the-activity-6922379400038547456-ptlJ