Problem of the day
Tip 1 : For company like codenation you need to be great in competitive programming as the online test is very difficult to crack
Tip 2 : Focus on leetcode during final months of preparation of interview
Tip 3 : Try to have at least 3 flagship projects in at least 2 different domains
Tip 1 : Keep the resume clean with good text to space ratio.
Tip 2 : Don't mention tech slacks that you have only a little knowledge about as it can backfire if the interviewer is good in that tech slack.
The test was from 10 pm to 11:30 pm at night, Since we had to give the test from home so it was not an uncomfortable timing for me. The test was conducted on hackerrank. Personally I find Hackerrank a better test platform than others like Amcat or Mettle.
The interview was at 12 noon.
This interview was at 10 am in the morning and was taken by an SDE 3 of the company who had a very great background in Competitive Coding.
The interview started with me introducing myself. The interviewer then gave me a google doc that had 2 coding questions written. He asked me to go through the first question and explain the approach. After which he asked me to code the solution as well. The same procedure was followed for the second question. The most difficult part in using Google Doc to write code is that it doesn't have automatic indentation like the code editors, so I had to put much effort in keeping my code readable.
I had read this article few days before the interview so I was aware of the approach that was efficient. But I started by explaining the naive O(N^3) solution.
The interviewer asked me to optimize the approach.
Then I gave him the approach I read in the article.
The interviewer asked me to code the solution which I did.
The round was at 4 pm evening. This round was taken by one of the Vice President of the company, this made me anxious from the very beginning.
The interviewer was a knowledgeable man and had great knowledge in every field. He always demanded exact answers.
Why do you want to join us?
Tell me about your projects.
Tip 1:Do not mention skills that you don't have much idea about.
Tip 2:Try to be exact with your answers and don't beat around the bush.
Tip 3: Do not ignore system design if you are aiming at good product based companies.