Technical interview: dos and don’ts
Tags: Interview Preparation, Interview Questions, Interview Tips

Job search is a nerve-wracking experience. I found it especially stressful because I have been working at the same place for the past 10 years. Although I changed a lot of roles and never stood still in my workplace, I did not need to apply for jobs and get through the interview process. “Personality” and “getting to know you” interviews turned out to be quite okay. Communication, dialogue and conversation is something I am really used to and rather good at.

The technical interview though was something I have not done before and was really difficult to anticipate what to expect. Here are some tips that I noted for myself after my first technical interviews.

Dos

Know your code and keep talking

Whether you were asked to build something or show one of your projects, it is important to revise the code before the interview and, perhaps, be prepared to explain some of the methods and functions you are using in your code.

Prepare couple of sentences about the coolest features of your project or, perhaps, how you came up with the solutions to certain code problems in the assignment. When asked a question you are puzzled by or do not know the answer to right away: just say it. Do not sit silent, start talking about your thought process. I think the process of problem solving is as important to your potential employers as the solution itself.

Stay positive and take the feedback well

If you do not know the answer, do not panic (I did), start a conversation about it and be positive. Something like: “oh, I have difficulty figuring this out, but I am eager to learn how to do it”.

You will probably get some feedback on your assignment or your project. I was very happy to get it, because I after the interview I got lots of suggesting on how to make my project ten times better. I mentioned that I appreciate the feedback and asked couple of follow up questions on the suggestions. It was noted by my interviewer as a very positive thing about me as a future colleague.

Take notes

As a junior developer you will probably, be asked the same questions during your interviews. Take notes, it will help you prepare for the next ones! For instance, I was asked about the difference between DOM and virtual DOM in two of my first technical interviews. I also got the same question about the difference between .map() and .forEach() methods.

Don’ts

Don’t try to pretend you know everything (they will figure out you don’t :D)

It is okay to say that you do not know certain things. Of course, it is great if you do. But I was told that, , if you know all about it, maybe you are overqualified for the job. Anyway, if you don’t, it is okay to say so and maybe ask the interviewer to explain it to you or again mention that you will be eager to learn it.

Don’t tell absolutely everything about your project

I was really over-prepared with my project presentation for one of the interviews. I told all about it: what I like, what I don’t like, what works, what does not work. And it took away a lot of potential followup questions from my interviewer. It was mentioned in the interview feedback, that I should have left more room for discussion about the functionalities of the project. So, be prepared to answer this type of questions, but, perhaps do not disclose all of the tricks right away.

Don’t despair if you failed

Something, that I still keep telling myself. After I failed my first technical interview, I started questioning my future as a developer. I felt like I do not know anything and should just go back to the job I know an do well and stop trying to pretend like I can do something else. The interview feedback I got, said the opposite though. Yes, at the moment I did not have enough experience to get the job, but they encouraged me to apply after I get little more knowledge, because I had a lot of potential.

I also realised that I have learned a lot after that interview. I certainly know now what closure is, what is the difference between let and var, how to write asynchronous Redux and many more things. If I am asked these questions again, I will be able to answer them and, perhaps, will land the job of my dreams!

What is your experience with technical interviews and tips to survive them?