Common Mistakes to avoid during your interview

October 30, 2017


We have compiled a list of mostly committed mistakes among our interviewees. Every Software Engineer should know about the no-no's, so identify if you display any of these traits and work on yourself to improve:
  • Speaking negatively of your current or past employer: avoid saying anything negative about your current or previous company, even if it’s true and it’s not that bad, it puts a negative effect on the interviewer’s subconscious
  • Talking not highly of yourself: when asked about a challenging situation or your worst failure, talk about something that was turned positive, and do not incriminate yourself
  • Spending too much time on background and behavioral questions: think about it as an elevator pitch (less than a minute). If interviewer wants to know more, she/he will ask specific questions
  • Jumping to proposing a solution without clarifying the question and all the boundaries, as well as talking about corner cases
  • Paying more attention to code details and cleanliness, than to logic of your solution: make sure your solution is correct and works for the main logic and the corner cases, then if you have time, you can work on polishing your code.
  • Asking for feedback from the interviewer too much: establish that you are in control, asking for feedback too frequently will send the signal that you need a lot of guidance and cannot work independently
  • Not telling the interviewer if you have seen the problem before: there are 2 issues here: a) Usually the interviewer can tell that you remember the solution by the way you approach it, so it might depict you as not completely honest. b) You might THINK that you know the solution. This might be just a similar problem to the one you've seen before, and a lot of details might be different, so you might actually might be putting your solution in a disadvantage by not telling the interviewer.
  • Trying to come up with the optimal solution right off the bat: do it the right way, and the way that makes more sense to you, eventually you can make optimizations. Otherwise you might confuse yourself

0 comments