 |
VOOZH | about |
|
VOOZH | about |
Recently, I attended an interview with Pal Tech. It is a well-known technology firm that provides innovative solutions. I was chosen based on my qualifications and academic background. There were three rounds for the interview: aptitude, coding, and personal interview.
It was an aptitude test, and the focus was on basic problem-solving skills, logical reasoning, and mathematical questions. The section was relatively simple and covered common aptitude topics, such as time and distance, profit and loss, percentages, and number series.
Apart from aptitude, there were pseudocode questions, which checked our ability to comprehend algorithms and logic, not getting too deep into any language. They designed the questions to test how well you could follow and interpret basic algorithms.
I found aptitude questions quite manageable, but for questions on pseudocode, I needed to read them carefully without getting caught up in mistakes or a misleading understanding of the flow of the program logic.
After clearing the aptitude test, I had to appear for a paper-based coding test. This consisted of three coding problems. The levels of difficulties were easy to medium. The problems are similar in difficulty to what you would face on LeetCode platforms, et cetera.
So basically, the first problem was quite simple, which consisted of a basic pattern generation problem. It was just so much about getting the loops right.
The second one was of medium difficulty. I was given the task of deleting duplicate numbers from a number. It required proper handling of data structures and logic to be efficient.
The third one on the list is tougher. The exercise concerns arrays and linked lists. I had to implement a solution dealing with common operations, which requires a good knowledge of data structures.
I was not allowed to test out the code because I had to write down the solutions on paper. The most important thing here is that the logic has to be sound and well-explained. Since there is no way of doing debugs, such an explanation proved to be more than essential. I was satisfied with my answers, though I did double-check my solutions for any edge cases before submitting them.
I was called for the personal interview after shortlisting from the coding round. That too was a comfortable one, where the interviewer turned out to be very friendly, making it comfortable to sit there.
Discussions on my projects kicked off the interview process. Deep questions were put in front of me relating to my role, the technologies used, and challenges faced while working on these projects. It was important to explain the architecture of the projects and how I thought of problem-solving in the development phase.
Technical concepts followed:
DBMS: Normalization, indexing, and transactions came under this topic.
Operating Systems: I was mostly questioned about process synchronization, memory management, and also very basic concepts such as threads and multitasking.
Computer Networking: Questions were asked about TCP/IP, regarding layers of OSI model, and a couple of case studies of real networking.
OOP (Object-Oriented Programming): I was asked to define concepts like inheritance, polymorphism, encapsulation, and abstraction by giving examples.
I also found that the technical questions asked were deep but fair. The person who interviewed me is not interested in the mere getting of textbook answers but rather on how you approach solving problems. Having finished the interview, I felt positive about my performance and confident about how I presented myself.
My experience with Pal Tech has been very intense and rewarding. The rounds were quite structured, and each round tested a different aspect of my skill set. So, preparation is the key, particularly in coding and core concepts of computer science.
