On the first day of the interview, I was asked to introduce myself. I began by saying, "My name is X, and I am from college Y." During my academic journey, I learned Data Structures and Algorithms (DSA), became proficient in C++, DBMS, SQL, computer networks, and problem-solving concepts. I also built a machine learning project that predicts house prices using various features. This project was based on a web application.
Before starting the actual interview questions, they first asked me some introductory ones. The first technical question was about finding the next palindrome date after 30-12-2103. The second question was about designing a system architecture for a book management system. I didn’t have much knowledge about system design, so I approached the problem by creating SQL tables and designing classes based on an object-oriented structure. I handled the system design question in this way, though I got confused during the first question. I wasn't sure whether I had to solve a Sudoku problem or handle something else related to the question.
Later, they asked me to explain my project, and I did so. They also asked questions about the machine learning algorithm I used to build it. Since the project was hosted online, I demonstrated it to them, and they were quite impressed. Afterward, we discussed the second question, especially around designing tables, features, and the uses of the book management system for about 10 to 15 minutes.
One of the key takeaways from the interview was that it's not just about getting the answers correct. It’s more important to clearly explain your thought process and make sure the interviewer understands your solution. Even if your answer is correct, if the interviewer doesn’t understand it, it doesn’t add value.