Coding Interview Steps

Its been 3 months that I started sharing my experience with community by guiding people from various colleges and companies. In this article I want to list down the sequences which will help one in mental preparation as to what to expect and how to lead the coding interview.

Most of the top tech company follows the clocked interview, let’s say 60 min round. This will involve introduction at a very high level or sometimes it might be skipped.

Once you have the question with you, take 2–3 mins to analyse it and come up with queries if its not self explanatory. Eg: time complexity needed, extra space can be used or not.

After clarification, take 3–5 mins to work on solution, visualising is a key concept here and don’t start writing on editor or paper.

Once above exercise is done, please make sure to take consensus on approach, and do dry run with interviewee if asked for, otherwise jump to coding. Keep time in mind. If interviewee is participating in dry run, this can be taken as hint as to either optimisation is needed or approach itself is invalid.

Last but not the least, make sure to lead the talk, if you don’t then interviewee might talk, if both are not communicating then there is higher chances of negative result.

planning += 1, assumption -= 1, practice *= 2;

Related posts:

Everyone is a Web3 native — native in the form that Web3 technology has become more of a necessity than just leisure. This means that everyone understands Web3 as their second nature. For a guy like…