Real, anonymous reports from people who interviewed for QA Engineer at Commvault, newest first and distilled into what to expect across the loop.
After a recruiter touchpoint, I went through a multi-round process that felt very QA-oriented but still heavy on fundamentals. Roughly a week later I had an online technical screen that combined a few programming problems with MCQs. The timing pressure stood out: the coding problems felt extremely hard for the time they gave, unless I was really comfortable with competitive-programming style problems. The MCQs mattered a lot, and when I focused there it felt like it helped more than I expected.
My interview journey was long and felt like it was designed to test me at multiple depths rather than one quick screening. After an initial OA, I went into a sequence that included a bug bounty-style round, then an LLD-style coding exercise, and then more technical interviews grounded in my resume and what I had worked on. There was also an HR touchpoint after those rounds.
The interview process begins with a timed online assessment that includes sections on aptitude, pseudo-code, and Python coding questions, all under strict time constraints. Candidates should be prepared for a mix of MCQs and coding problems that test computer science fundamentals and reasoning skills.
A hands-on debugging round follows the initial assessment, where candidates are tasked with identifying issues on a provided test website. This round emphasizes practical QA skills and the ability to reason through problems, reflecting day-to-day responsibilities in the role.
Subsequent technical interviews delve into operating systems and networking concepts, with an emphasis on applying knowledge rather than rote memorization. Candidates should expect in-depth discussions that assess their understanding of system behavior and testing principles.
The interview process is designed to increase in intensity, with each round building on the previous one. Candidates should be ready for a variety of question formats and to demonstrate their problem-solving abilities under pressure.
An HR interview typically concludes the process, allowing candidates to discuss their experiences and fit within the company culture. This step is important for assessing alignment with the company's values and expectations.
Candidates noted the importance of focusing on core QA principles and system fundamentals rather than traditional coding puzzles. Familiarity with Python and the ability to articulate testing strategies are crucial for success.