You’ve been coding for a while and are ready to translate your tech know-how into a j-o-b. Yet, few things can inspire as much sweat as a sea of seasoned software engineers drilling you with challenges. Nailing your technical interview is an integral part of the hiring process, so gear up. Three web development wizards share their tips to interviewing for a coding career with confidence.
Before the Interview
In preparation, Marc Wright, lead instructor of the Web Development Immersive Program at General Assembly, says you should “Find out everything you can about the position/tech used before the interview. I also ask the HR/recruiter person if they have any insight as to specifics I should prep for.”
Max McChesney, partner and campus director of DigitalCrafts, suggests also finding the right coach to prep you: “There’s no practice like the (semi) real thing, and finding someone who would be willing to play the employer on the other side of the table shouldn’t be difficult. If you’re thinking, “I don’t know any developers/managers that could play the role well,” then get networking. Find a JavaScript/ iOS / ____ meetup in your area and get networking. The people who run these (typically free) events are often well-known names in the local tech community, and they’re usually very approachable and willing to help.”
Make sure to make a list of your projects and the thought process behind each one of them, says Pamela O. Vickers, software engineering manager at MailChimp and the head of Rails Girls Atlanta. “Being able to answer questions articulately about technical decisions and the architecture of previous projects shows that you both understand what you’ve done and that you actually did the work. If you feel rusty on lots of details on a previous project, try to refresh your memory or consider taking it off your resume.”
And don’t forget: “Arriving 10 minutes early is on time! Demand for developers has been so high in recent years that the common courtesies of interviewing seem to have withered away for most candidates,” says McChesney. “Show up prepared, on time, and looking presentable.” Also, find out who you’ll be interviewing with, says McChesney. “Mention that you really liked their YouTube channel or blog (that they’re likely very proud of), it’s going to put you in a positive light.”
During the Interview
Can’t think of the answer? Work through the problem out loud, if you can. “When in the actual interview, don’t go silent when you begin thinking over a problem,” says McChesney. “Good interviewers aren’t necessarily looking for perfect syntax and structure, they’re looking for your thought process. This is especially true when interviewing for junior-level positions. Start talking through the problem, and make sure you ask questions! Software doesn’t tolerate assumptions very well, so make none in your approach.”
Wright agrees. “Communication is super important in general so make sure you verbalize what you’re thinking.” If you’re not sure, “don’t be afraid to say you don’t know something,” says Wright. “I think it’s better to be honest than fake it. Maybe mention a similar technology that you do know that may solve the problem. Or, you can speak to times when you’ve had to learn a new technology and implement it. Focus on your ability to adopt new things.”
Vickers suggests going for an educated guess, if you can. “If you’re unsure but want to venture an informed guess, go for that partial credit! But again, make your thought process clear so they know why you’re answering the way you are.”
After the Interview
If they ask about a previous employer or team member, Vickers advises “to be careful, when talking about previous projects or jobs, to not disparage the decisions of your teammates — especially when you disagree with a technical decision. This is a great way to show that you can make good judgment calls while still being a respectful team member.”
And of course, “make sure to write a ‘thank you’ letter after the fact,” says McChesney.
Other Resources
Find experts and learn from them. An example is Gayle McDowell, who is a prolific writer regarding technical interviews. Consider checking out her “Cracking the Coding Interview: Unscripted Interview Videos” (though they’re not free). The only other issue with her resources is they’re often overly difficult or complex for entry-level positions. If you’re going after that engineering role at Google, they might be a good bet.
That said, there are tons of free “code challenge questions” available online, like Interview Cake, a daily email with challenges to keep you sharp, and Enki, an app with bite-sized web development quizzes. So, just look around. Don’t forget that Github is a rich resource. For example, here are some JavaScript Code Challenges that are much more inline with what junior developers may see on the job hunt.
