4 Common Mistakes In Coding Interviews

Here are 4 common coding interview mistakes and how to fix them. If you want to pass the coding interviews, you need to avoid these mistakes, and you need to follow these coding interview tips.

[moshiurrahmanmoshi]

To save time of you guys, 4 common mistakes he trying to tell:
1. Over-communication
2. Listing out a bunch of DS, Algorithms with explaining why they could solve it
3. Not buying AlgoExpert/ Jumping out to the coding without any thought about how they are going to code
4. Not confirming with the interviewer what the problem statement is.

[finalbox]

If Clement was a McDonalds recruiter, I think he would still run every candidate through a coding interview.

[basslinr]

I just came off a pre-interview meeting (basically with the recruiter) and the recruiter said at least 50 times "communicate everything" "explain your thoughts"
which sounds the opposite to what you're saying.. however I think what you mean is to communicate effectivly.
This guy made a good point he said that they want to get an insight in to your thinking and problem solving process.
I think there is probably a middle ground between rambling and not saying anything.

[chair_smesh]

This is great. I feel like I always have to read the question out loud over and over again when pair programming in Bootcamp. It would be nice to take a minute to silently process the question

[PandaZelda]

Yikes I just applied for a coding bootcamp and am new to this world — definitely noticed myself making the over communication mistake during my interview haha 😂 these are great tips to keep in mind

[sea]

None of these even matter. If the interviewer doesn't like you for any reason, you will be rejected no matter what. They will not even tell you why you failed. They can come up with any reason. You talked too much/too less, didn't say confidently, asked unimportant questions, didn't have good attitude, whatever. You will realize it once you become good at coding questions and interviewer reject you regardless.

[zinsy]

I would say this is applicable with troubleshooting in general! Mistake #4 is what I screw up the most! It takes me a while to realize I'm actually solving the wrong problem or looking at the wrong thing in the first place! This is one of my main weaknesses I'm working on at the moment.I'm trying to recognize that early on and see if there's a quick way to prove/disprove the conclusion I've jumped to for what I'm solving. Doing that either leads me right to the solution or on the right path to finding it!

[sjamr]

JIT, I have a coding interview on Monday and was actually thinking about overcommunicating because I thought it was good lol.

[KaroCodes]

For years I thought over-communication in case of engineers is impossible so I always advised everyone to *communicate more*. Then I joined a team of extroverted engineers... OVER-COMMUNICATION. DOES. EXIST. 😫

[alexeykorovko]

a lot of people say that the mistake is to be too silent, but actually over-communication is not better at all. I'd seen this video and cached myself on this. I I think when you talk too much, the interviewer gets confused and doesn't understand what's really happening

[MdWahidurRahmanOvi]

Thank you for not mentioning or bragging about ex google employee or ex FANG employee. As always great content and thank you again.

[clydedsouza]

Algo Girl - "So you wanna be a software engineer at Google?"
Me - *No! Because I am a freelancer!*

[JoLap]

Coding interviews = seeing how good you are at memorizing Leetcode solutions. It's sad that this is what the industry has become.

[crazychase]

Wow Clement, I don't remember giving you the OK to make a documentary video about me!

[LilyEvans]

Starting to go through interviews now and it’s so scary! Especially for big tech companies

[mcog]

If this came out 3 days earlier I'd have aced my coding interview... Mistake number 3 got me on a an easy coding problem.

[markyjordan]

FYI, for those wondering, regarding the approach of converting an array to a BST mentioned at 4:02 to allow for logarithmic searches, this would only be an interesting optimization technique if the input array was sorted, because if it is unsorted, the time complexity of the conversion operation would be O(n log n), which as we know isn't an improvement on the O(n) linear search.

[vasujain]

Hey clement, appreciate such videos, continue putting such content!

[gaurakhandelwal]

Hi Clement, awesome content like this really helps people like us, very insightful. Would remember these points, last time one of these mistakes dropped me out.

[aoeu]

Jumping in to code could work using constraint, test code, and top down coding in a high level chatgpt based language. It however does not work when your coding in a low level language….