By February 12, 2019

Developers ALWAYS Make These Coding Interview Mistakes

Did you know that a lot of developers make some simple mistakes that can totally ruin the way they'll perform in coding interviews?

If they make these mistake and you don't, you're in total advantage when it comes to getting a new job.

When searching for programming jobs, developers often face a step that they fear: coding interviews.

00:12 – Being Late
00:53 – Casual is Ok
02:16 – Now Knowing The Company
03:00 – Now KNowing Your True Potential
03:50 – Not Being Grateful

In today's video, we are going to talk about some common mistakes developers make all the time in coding interviews and how you can avoid them next time you went to your coding interview.

Coding Interview: My 5 Top Tips To Succeed

Transcript Of The Video

Jason Humphrey:  As subtle as it is, you wouldn't believe how many people I see fall victim to it every single day, in coding interviews. Now, let's jump into it. First and foremost, being late. That sounds so subtle and simple that, how is that falling victim? People fall victim to their clocks, their times, all the time. It's one of the easiest ways to make a really bad impression in the very beginning.

Do not be late. If you're not early, you're late. Let's leave it at that. As it is, you should try to show up 15 to 30 minutes early. Point being here though that, not everyone always likes you being super early, because then they have to go get you. Point is, you need to be early, period. Don't fall victim to thinking, “Oh, I'll show up right on time, everything will be good.” No.

Second point. Casual is okay. Yeah, no. No, no. Mm-mm (negative). No. I say this because far too often, people will come in and think and speak like we're best friends, or we're cool. They think that this whole casualness is kosher, when really it's not. I don't know you. You don't know me. You need to be respectful of the work environment. You need to show respect for what you're interviewing here with. That goes also to the dress code. People think and read online, “Oh, it's a casual company. They wear jeans and pajamas into work.” Great. Don't do it. Do not fall victim to this idea of casual is okay at these companies.

You need to dress for what you want to be like, and dress how you want to act and not fall victim to dressing down to how you want to be. Yeah, I get, once you're in the job, great, you wanna wear jeans in, fine. Not in your interview. You need to dress to impress. You need to speak to impress. Don't use improper grammar. Don't use slang. Be direct. Don't be vague. There's lots of little things in there. I get that. Casual is not okay. Do not fall victim to thinking casual is okay. You don't have to wear a tuxedo by any means, but a suit and tie would help. Let's leave it at that.

Now, not knowing the company, people fall victim to all the time. More often than not, whether it's a mock interview, whether I'm helping a student out, wherever I am, I ask because mock interviews generally have fake companies. I ask them about the companies. I ask 'em about that. Even in the mock interviews, they fall victim to it. What do you thinks gonna happen in a real interview, when you have no idea about this company in Atlanta, that's still owned by the founder, that has extreme pride in Atlanta, that really loves their culture and you know nothing about it. Don't fall victim to thinking that you are just coming to do an interview and you don't have to know the culture, you don't have to know anything about them and not knowing the company. You can just come in.

Now, on the flip side, don't fall victim to not knowing your own worth. Far too often, people will come in and not realize what their worth or talk about what they're worth. They fall victim to this, letting people think that they're just, “Oh, I'm just a developer,” or, “I'm just this one thing.” You don't know your worth more. You're worth more as a leader, as a leader in code, as a communicator, as a team player, as all these soft skills, that you really are, but you don't know your own worth, so you don't portray 'em. People fall victim to that time and time again. I encourage you, to know your worth, know … That's not just a monetary value. It's what you bring to a team. It's what you can actually do when you're in the job, and what you're doing already.

Lastly, don't fall victim to not saying thankful, being grateful, or showing gratitude. It's not to say that the people that you're interviewing with, walk on water by any means. No. The fact they were willing to look at your resume, bring you in, take their time out of their day, to talk to you, time is our most precious asset. Let's be honest about. The fact you're not gonna thank them for them taking their time, because your time might potentially change your life, but them taking their time out of their day to meet with you, is huge. Don't fall victim not saying thank you to everyone on the team that you get to interview with, and show an appreciation and gratitude, because it's only gonna help you be personable.

These are the main things within don't fall victim to. Do not fall victim to being late, and that casual is okay, not knowing the company, not knowing your own worth, and not saying thank you. You follow those five things and it will immensely help you not fall victim to some of the most common things I see in interviews on a daily basis. Let me know your thoughts. Feel free to leave a comment. 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.