I got a call directly from their HR team saying my profile had been selected for a Lead Performance Test Engineer position. I went in for an interview on the weekend, where the interviewer basically asked me to introduce myself and then quickly told me they were looking for something else. It felt sloppy, because the resume and my fit didn’t seem to have been reviewed properly, and I walked away thinking the whole thing could’ve been handled more professionally.
> 1 year
Easy Positive Mumbai
My interview journey moved in a clear sequence of rounds. First I had an aptitude-type assessment that set the tone, and it felt a bit tricky—especially from the perspective of automation testing where the aptitude portion was noticeably harder. After that, I went into a discussion-style round about whether AI is dangerous or not.
Next came the technical interview where the interviewer tied questions back to my projects. I was asked about how many requests I could send to the server, which was the kind of practical scaling/thinking question that stood out to me. The final step was an HR round where the conversation shifted away from testing detail into personal logistics, including whether my family would support me and how workable the situation would be given that Mumbai is expensive and the salary level I was expecting.
> 1 year
Average Positive Navi Mumbai
My experience followed a pretty common multi-round testing path: an aptitude round, then a technical interview, and finally HR. What surprised me was …
> 1 year
Difficult Positive Mumbai
I went through a three-round setup where the first technical round was the real stress test. It was described to me as very tough, and when I was sitt…
> 1 year
Average Positive Mumbai
My first contact came through a virtual sequence, and the early rounds moved fast with fairly quick HR responses. The structure then stayed consistent…
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
The interview process typically follows a structured sequence starting with an aptitude test, followed by one or two technical rounds, and concluding with an HR discussion. Candidates often report a clear progression through these stages, with a focus on elimination at each step.
Aptitude testTechnical roundsHR discussion
Technical Focus & Content
Technical interviews emphasize core QA concepts, manual testing, and Java fundamentals, with questions often related to real-world scenarios and project experience. Candidates are expected to demonstrate clarity in their understanding of testing processes and tools like Selenium and SQL.
Manual testingJava fundamentalsSelenium
Behavioral & HR Interaction
The HR round tends to be conversational, focusing on fit, logistics, and salary discussions rather than technical grilling. Candidates often find this part lighter and more about confirming details than assessing technical skills.
Overall, candidates describe the interview environment as welcoming and supportive, with interviewers aiming to understand the candidate's fit rather than creating a high-pressure situation. However, some candidates noted inconsistencies in communication and scheduling.
Supportive environmentCommunicationScheduling
Difficulty & Expectations
While many candidates find the technical rounds manageable, some report that the initial technical assessments can be challenging, particularly for those with less experience. The expectation is to demonstrate solid foundational knowledge rather than advanced or obscure topics.
Candidates have experienced varying lengths of the interview process, with some facing delays and communication gaps, particularly in the later stages. This can lead to frustration and uncertainty about the status of their applications.