![]() |
VOOZH | about |
Out of 3,147 applicants, 595 students were shortlisted for the online assessment. The selection was based on multiple factors, including resumes and academic performance, with cutoffs often significantly higher than the stated minimum eligibility criteria. The process began with the Vellore campus candidates.
This was an MCQ-based test, concluding with two coding questions. Key highlights:
The MCQs covered:
The test was conducted on the HirePro platform, and from 595 participants, 131 students were selected for the interviews. Among them, 62 were from the Vellore campus.
Time: 1-1H20Min
This was the first technical round, with significant variability depending on the interview panel. The panel, consisting of two interviewers, asked in-depth questions to assess knowledge of core computer science subjects, system design, cloud services, and data structures and algorithms (DSA).
For me, the interview focused heavily on AWS (as I had listed AWS Solutions Architect Associate on my resume), followed by other core areas such as:
Notably, some candidates were asked DSA-heavy questions or were questioned extensively on their resumes, underscoring the variability in the interview experience.
By the end of the day, 15 students out of the 62 were selected for the next round.
Time: 1-1.5H
This round focused primarily on resume-based questions, especially regarding projects, internships, and certifications. The interview was quite challenging, demanding a deep understanding of concepts.
For me, the focus was on Database Systems:
They also tested my problem-solving skills by asking me to optimize my previous project using available online resources and had me build an optimal solution for Fibonacci Numbers, explaining concepts like time complexity, overlapping subproblems, and dynamic programming.
Out of the 15 students, 8-10 candidates advanced to the final HR round.
Time: 0.5-0.75H
This was a more relaxed, conversational round, focusing on personality and career aspirations. I highly recommend thoroughly researching the company's background, leadership, and values, as it helped me give well-informed and relevant answers.
The questions included:
The interview concluded with a discussion about location preferences. It felt more like a conversation than a formal interview.
The results were announced the following day, and out of 15 candidates, 7 were selected. I was fortunate to be among the selected candidates.
This experience was a comprehensive process, testing not only technical knowledge but also adaptability, problem-solving skills, and interpersonal abilities. Preparing thoroughly for both technical and non-technical aspects is key to succeeding in such interviews.