There was a coding round on hackerrank, consisting of 2 coding questions and 10 MCQs, followed by three rounds of interviews, two being technical interviews and one HR interview at the end.
The coding round had random questions, and I was lucky enough to get the simpler questions.
The test was on Hackerrank. I don’t remember the exact questions, but they were fairly straightforward and easy.
The first interview was a technical interview. Shortly after the test, a shortlist for the interviews was released and we had the interviews in the morning at 10.
The first question was based on the Data Structure, Linked List:
Given a linked list containing numbers, find the n’th largest number without manipulating the list, and without using any auxiliary data structures.
The second question was based on the OOP concepts. He wanted me to explain all the principles of OOP using examples from the room I was sitting in.
I was then asked a riddle – If the hour hand of a clock stops moving but the minute hand works well, then how many times will the clock show the correct time in a day.
Finally, he asked if I had any questions for him.
This was the first ever interview I sat in. I was very nervous and had little time to mentally prepare myself post receiving the shortlist for the interview, as a result of which, I was unable to answer the first question at all. I did manage to answer the other questions and qualified for the next round.
The second interview was also technical, and was on MS Teams platform. I was asked two questions in this round.
The first question was to assess my knowledge of DBMS. I was asked to design the database of a clinic. I asked questions like are there more than one doctors in the clinic, and so on. I started naming entities in the air, and the interviewer asked me if that was the perfect way to explain things. I realized ER Diagram is the way to go and opened draw.io to make the ER Diagram of the database. It’s better to be familiar with such tools beforehand, rather than try to figure it out on the fly, like I did.
I was then asked to write SQL queries on the database I designed. The SQL queries typically involved joining tables. I knew conceptually how to solve the problems posed, however, I was not well versed with the syntaxes and made a couple of mistakes that could have been avoided.
Next, I was asked to write code for Deletion of a node of a Binary Tree.
Finally, he asked if I had any questions for him. I asked him one question.
Third Interview: HR
Finally, after 2 interviews, I had the HR interview on the next day. The HR interview was less tense and revolved around questions such as tell me about yourself, how the interview exp was, how the 2 years of college were and so on. I feel it is important to know about the company, and ask questions about the company in this round, so that the HR feels one is interested in the company.
After the three rounds, 2 people were selected. I was not one of them.
- Maintaining a good CGPA is a must as it helps in getting shortlisted.
- Practise coding questions from standard platforms, such as Leetcode, Interviewbit and so on.
- It is also favourable to practise some of the aptitude questions, as quite a few of the companies ask these. They are easy questions, however, solving them correctly in a short amount of time is pretty challenging.
- Luck plays an important role in the whole process. It is fairly natural to be disheartened after a few rejections. Look at the rejections as stories to learn from.