After an initial recruiter touchpoint, the process moved quickly into technical work. A week later I got a virtual coding assessment with a time limit of about 45 minutes, and it felt fairly hands-on: I ran through two short programs that were closer to easy-level problems, one involving Java stream usage and the other focused on API testing. What stood out was that it wasn’t just theory; it expected practical thinking with code.
Following the coding round, I had a larger technical conversation. It leaned toward automation-oriented knowledge and framework-style thinking, with questions that started from basics and then went deeper if I showed I could handle them. I was asked about areas like promises and event-loop behavior, plus general JavaScript fundamentals such as array methods, and I also got questions tied to test automation tooling and structure (including configuration and page-object style organization). The difficulty felt average overall, but the pace and the jump from fundamentals to troubleshooting made it stressful—there was a sense that one or two gaps could swing the decision.
4 months ago
Difficult Positive Mumbai
My interview process felt compact, but the first technical stage was intense enough that it set the tone for everything afterward. The initial round itself was basically a long drill—around two hours—covering a wide sweep of QA-related topics. I had to stay sharp across fundamentals and edge cases rather than rely on one narrow strength.
After that came a managerial-style discussion focused on both testing concepts and how I approached managing work. That part was harder to read because it mixed technical understanding with expectations around direction and decision-making. I then completed an HR round where the conversation was more straightforward, but by then I was already mentally drained from the earlier pace.
7 months ago
Average Positive Chennai
My process followed a pretty clear arc: an HR screening call first, then an in-person technical interview, and finally another HR discussion for next …
8 months ago
Difficult Negative Pune
A lot of my experience wasn’t about the content of the questions—it was about the timing and coordination. I had a scheduled interview and showed up t…
10 months ago
Average Negative India
My interview experience was heavily shaped by how strict they were about matching a preferred automation style. In the technical discussion, they aske…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial HR Screening
The interview process typically begins with an HR screening call that covers background, role fit, and logistical details like salary expectations and notice period. This stage sets the tone for the rest of the process, focusing on communication and overall alignment with the role.
HRBackgroundRole Fit
Technical Assessment
Candidates can expect a rigorous technical assessment that often includes hands-on coding tasks, covering a range of topics from QA fundamentals to specific automation frameworks. The interviews are designed to evaluate practical problem-solving skills rather than just theoretical knowledge.
CodingQA FundamentalsAutomation
Focus on Automation and Tools
There is a strong emphasis on automation tools and frameworks, with questions about specific technologies like Selenium, Playwright, and Java-based testing tools. Candidates should be prepared to discuss their implementation styles and how they align with the company's expectations.
AutomationSeleniumPlaywright
Managerial and Behavioral Rounds
Following the technical rounds, candidates often face managerial discussions that assess their approach to project management, decision-making, and team dynamics. These conversations blend technical understanding with soft skills and cultural fit.
ManagerialBehavioralProject Management
Interview Atmosphere and Communication
While the technical rounds can be intense, many candidates report a generally respectful and professional atmosphere. However, feedback and follow-up communication can vary, with some candidates experiencing delays or a lack of constructive feedback post-interview.
CommunicationProfessionalismFeedback
Process Coordination and Timing
Candidates have noted that the coordination of the interview process can impact their experience, with some facing long waits or delays that affect their performance. Ensuring timely communication and organization is crucial for a smooth interview experience.