By January 31, 2019

Don’t Make These Coding Interview Mistakes (#2 Is About Money ๐Ÿ’ต )

There are three basic mistakes developers make ALL THE TIME in coding interviews that can destroy any chance of getting a programming job. #codinginterviews #programmingjob #programming

I've categorized these common mistakes into three big groups:

00:20 #1 Your Resume
03:32 #2 How You Talk
05:38 #3 Body Language

If you don't make these coding interview mistakes developers make ALL THE TIME you'll most likely succeed at any coding interview.

4 Coding Interview Questions You Should ABSOLUTELY Prepare For
https://www.youtube.com/watch?v=Xk4iDSCrTzU

Transcript Of The Video

Jason Humphrey:ย ย This video is all about the three common mistakes I see in coding interviews today, and then I want to help you fix right away. They all revolve around three things, your resume, how you talk, and your presence. Let's talk about your resume. The first common mistake I see people fall to all the time is not knowing your tech or your projects well enough. People put these great big stories or projects, or things that aren't necessarily, they're true, but let's keep it right, they are true, they maybe went to AWS and started their certification, or maybe they did build part of a commerce site, or maybe they did do some type of roller responsibility. But when it comes down to it, they can't seem to answer the insight questions. And, if you'd seen the other video from before about the four types of questions, that's what I'm getting back to.

The insight questions, this is where not knowing your tech and your projects enough is a common mistake of people don't then have good insight answers to the projects they are working on. The technology they've done. Those questions are meant to validate and see what you have learned, and if you cannot show validation in the sense of what you're putting on there is true, or is good enough as to what you proclaimed it was on your resume, or you can't answer questions about it, it's a very common mistake that I see that it's just like, “Well, another one bites the dust.” Sorry, I break out in song sometimes, I thought that'd be a fun one. That's the first common mistake inside a resume.

Another one inside of resumes is not answering the questions. When people ask about around certain areas that maybe aren't directly talking to your resume, maybe aren't directly talking to the tech, but they don't answer to questions that based on what I see tells me you should be able to talk about how lambda functions work, or talk about how you write a handler with no JS for a lambda function. And, maybe you get into … So, this is where like they might be saying Amazon on their resume, but down inside of it we're going to ask you about a handler function and how maybe inside the lambda works and how that all works, and then they can't answer the questions.

The third in a resume, common mistake I see is the tech responsibility inside your resume to be able to show the language. Like you know enough about your language, you can demonstrate your resume, talks to it. Your experiences can show it, but pointing the technical responsibility inside of the resume is to say or to show the base of knowledge, the base technical expertise they have that deems them worthy of this job, or this interview, or where they're at. And far too often when you start out, I know in the beginning its hard to have all that, but you can certainly learn all of it. And then not, not put that on there. You can put it on there and be able to talk to it and have experiences on there. So, within resume you should know your tech, know your projects, be able to answer questions, anything on it and have displayed technical expertise to the level of what you are trying to interview for.

The second common mistake I see is how people talk in interviews, or what people talk about and their confidence within talking specifically is the first one. And, I've talked about this and some other videos, how people question themselves and have self deprecating talk, that's one of the first things they do. The second thing inside of talking is money. They talk about money like please do not talk about money in the interview. More often than not now HR people or recruiters are the only ones that are allowed to talk about it unless it's a really small company and you it's a small shop, but more it's not it's left to recruiters in HR. So, please do not come in to a technical candidate, or to the manager right away, or any of them unless it's prompted. Don't talk about money.

Don't talk about how you don't want to lose shares or don't talk about how like, “Oh, hey, this is a lot of money. That's what I'm here for.” Do not make it about money. I've seen plenty of times to where I wouldn't want to say too many, it's not crazy amount, but I've seen enough to know better that people should think about it more and be conscious of this is not about money, this, and this leads me right into my next point. It's about the situation you're interviewing for. I've also seen people not just talk about money, they've talked about, “Oh, I just can't wait to get out my current situation. I can't wait to get to a better team.” And then it becomes, well, it's now not about our team, it's about you just getting out of your situation and you could care if it's us or McDonald's. Right?

And can you use that example over and over again in this playlist. But it's about you leaving the situation. People do that all the time and it's not just like, you can't be just looking for an exit out of something. So don't do that. Don't do it. It's too easy to do, to fall into that trap where people make that mistake and talk about money, leaving their current situation, looking for an exit or not wind exit because of money or some other nature. So be careful how you talk, those are some of the most common mistakes I see within how people talking in an interview that gets them in trouble very, very quickly.

My last one, my last common mistake is the presence in the room. That's peoples, it's very common mistake most people don't actually talk about and that I want to make sure we talk about here today. And that is, when I say your presence in the room, this is all about your body language. Far too often people come into an interview and you'll see their demeanor is very closed in. It's very like, they're covering themselves, they're playing with their hair, like it's not just they're closed in and they are unconfidence, like the nervousness kicks in and I get this is a tough situation, right? Coming in for an interview that could change your life. I get it's hard, but the presence in the room speaks volumes to you as a person and to you as in the interview.

People all the time don't even acknowledge us when really the presence in the room, if you are very open, you're very, like your voice is projecting and you're not cowering back. You're not closed off, you're not pulling your arms like this under your armpits like and you're being very open. You're being honest, you're giving your best foot forward and you're, you have a good presence in the room and people know that you're there and like you were interested and you're engaging in. The mistake is far too often, it almost feels like you don't want to be in the room because you're so nervous, or so unconfident that it is a huge mistake people make all the time. I'd much rather see you set up, project your voice, open chest and be very confident with everything you say, or at least try to be confident. Act as if you're confident, and so that is the third mistake. Overall focusing on what you're saying on your resume and being able to talk to is really the most common mistake I see.

The second most common mistake is people talking about things they just shouldn't. In the sense of whether it's money, or leaving the current situation, or looking to get out. Don't talk about those things and while you're looking for a job, not worth it. And third, and lastly, the presence in the room can make all the difference in how the interview goes and how the outcome is. That would be a timer, I'm right on time, perfect. If you guys have any questions, feel free to leave a comment or question down below and when we happen to get to that, there'll be some more videos coming out in this area. Especially, I know we're going to talk more about technical responsibility. If you haven't seen some of the ones on getting ready, preparing, coding interview 101. There's a lot of other great stuff coming out and I will see you guys in the next video.

About the author

    Jason Humphrey

    Jason Humphrey is an full stack development, entrepreneur and investor. He is a professional programmer and engineer working in Node js, Angularjs, HTML5, CSS, JavaScript/jQuery, Mongodb, and Jive. He is a full stack developer, with a special emphasis on and passion for MEAN stack. You can find more about him on his website.