Xoriant Qa Engineer Interview Questions
& Process

The interview process started with a telephonic round focusing on basic Java, OOPS, and collection concepts. This was followed by a face-to-face interview that delved into my past roles and responsibilities, along with questions about Rest API and AWS. The next round was with the delivery manager, where we discussed process-related aspects in a relaxed manner. Finally, there was an HR round.

I was referred by a friend who works at Xoriant. The process seemed straightforward: first, a Technical Round, then an HR Managerial Round where package discussions happen after. If both rounds were successful, a client round would follow. I applied with multiple skills, like Mobile and Web App Testing, and Xoriant considered me for both. I cleared the first two rounds and then discussed the package. After some negotiation, we agreed on a package. Then, I was informed that the positions for Mobile Testing were closed and they'd let me know if other openings arose. The HR person I spoke with was knowledgeable. I mentioned to HR that I had more experience in Web apps than mobile apps. When I asked about the supposed positions for both mobile and Web apps testing, I was told they were closed and they'd keep me updated. The client round never happened. I have some queries about why the interview was conducted if there were no positions, and if the package was the issue, since I had agreed to their offer. People invest time in interviews believing the company is good, so situations like this make one question Xoriant. My suggestions are: be clear internally about hiring needs to avoid wasting candidates' time, finish interviews as planned instead of giving excuses about client positions being filled, and be transparent about the actual reasons. If there's no transparency now, I doubt the company will be good to work for in the future.

The interview was a really tough questionnaire. It covered programming to sort an array in descending order, Selenium WebDriver questions, Cucumber hooks and their execution order, Maven build goals, and Jenkins GitHub integration using Webhooks.