Commvault Test Automation Engineer Interview Questions
& Process

So after an online assessment, a bug bounty, and a low-level design coding round, I had my on-campus interview. It consisted of two rounds that were resume-based and related to the test job, and then HR was after those two.

So the interview was all about software testing, really in-depth. They didn't really hit me with any development questions, and no data structures or algorithms stuff either. It was heavy on computer networks and operating systems, though.

The interview process for the SDET role (Automation Engineer, Python) was quite lengthy and ultimately disappointing. After an employee referral, I underwent three technical phone interviews that covered basic concepts in OOPS, OS, compiler design, and networking. Unfortunately, the interviewers seemed unprepared, with one even reviewing my resume just before our call. The subsequent on-site interviews, which lasted from 9:30 am to 5 pm, comprised five rounds. The initial round with a project manager was too casual and lacked focus on my background; instead, I was peppered with theoretical OS questions from my undergraduate studies. A senior engineer conducted the second round, which went well, involving questions about my resume, C++, and a quick puzzle. The remaining three rounds with other engineers were also decent, though I sensed a lack of deep knowledge among them, and one interviewer resorted to searching for questions online, especially after I corrected him on a couple. The overall experience was subpar, marked by poor communication from HR and a lack of professionalism from the engineering team. Despite a friend's assurances about the learning opportunities, the company's rejection after three weeks with an illogical reason, combined with the 6-7 weeks I invested, made it a negative experience.