I had a relatively straightforward experience compared with what I’d heard elsewhere. The process started with a phone screen and then moved to an onsite interview. Onsite, the questions were a mix of QA fundamentals and more personal parts like my achievements, my goals, and my work experience. It didn’t feel like they were trying to trick me; it felt more like validating whether my background lined up with what they needed.
In the onsite conversation, the manager and team leader asked about my fit for the project objectives and how my skills and education connected to the type of work I’d be doing. The atmosphere was easy enough that I wasn’t second-guessing every answer.
> 1 year
Average Negative New Delhi
The process I went through stretched across five rounds, and it felt a bit like trying to match the role to a moving target. I took an online test first, then a technical interview with a lead, followed by another technical step with a manager. After that came an HR round and then a global-style discussion.
I cleared every round, which made me feel pretty confident by the end. The HR call after the final feedback said the partner’s feedback was that I wanted to explore newer tools and technologies, and that was the reason they didn’t feel I fit for the given role.
> 1 year
Easy Negative India
My interview journey took a lot of steps—around six rounds total—which made it feel like a serious time investment. It included a written test, multip…
> 1 year
Average Positive Gurgaon, Haryana
My process felt surprisingly smooth and tightly scheduled. I started with an online test, then had two technical rounds, followed by a manager round a…
> 1 year
Average Neutral Austin, TX
I went through an HR screening phone call and then had an interview with the hiring manager plus two engineers. That technical session lasted about an…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
Candidates typically experience a structured interview process that includes a written test, multiple technical interviews, a managerial round, and an HR discussion. The number of rounds can vary, with reports indicating anywhere from four to six rounds in total.
multi-roundwritten testHR discussion
Technical & Automation Focus
Interviews emphasize technical knowledge, particularly in QA fundamentals, automation frameworks, and testing methodologies. Candidates should be prepared to discuss tools like Selenium, C#, and BDD concepts, as well as demonstrate their problem-solving skills through scenario-based questions.
SeleniumC#BDD
Behavioral & Fit Assessment
Interviews often include discussions about candidates' backgrounds, achievements, and fit for the team and project objectives. This aspect aims to validate how candidates' experiences align with the role's requirements and the company's culture.
behavioralteam fitexperience alignment
Communication & Feedback Issues
Several candidates reported a lack of clarity and communication from HR regarding the outcome of their interviews, leading to feelings of uncertainty and frustration. Follow-up responses were often vague or delayed, leaving candidates without clear feedback.
communicationfeedbackuncertainty
Interview Atmosphere
The interview environment is generally described as cooperative and supportive, with interviewers engaging positively with candidates. This atmosphere can help alleviate stress during technical discussions, although some candidates still felt the process was overly fast-paced.
supportivecooperativestress management
Outcome & Closure
Despite performing well in interviews, many candidates did not receive offers, often without clear explanations for the decisions. This lack of closure after multiple rounds can leave candidates feeling their time was not respected.