My process was short and mostly virtual, and I could feel that they wanted to keep momentum. HR initially reached out and scheduled my first level interview, and once I cleared that stage, the next interview was lined up quickly—followed by an HR discussion the very next day. Everything happened virtually, so I wasn’t traveling or dealing with in-person logistics.
The format ended up being a mix of technical and final stakeholder-style evaluation, with a couple of technical rounds before the last discussion. I remember it as pretty smooth and well coordinated overall, with the panel able to get the next schedule quickly if someone wasn’t available. The conversations also included practical role scope and responsibilities, so it didn’t feel like they were just grilling trivia.
11 months ago
Difficult Negative United Kingdom
My first impression of the process was pretty rough. I started with an online technical round where the questioning felt like rapid-fire core topics, and the interviewer didn’t even have video on or give much time to think. I managed to answer most of the questions, but the overall experience left a bad taste.
I then moved to a second round, but scheduling problems piled up. It got rescheduled twice, and the meeting ended up being moved just about an hour before the interview. The second technical round followed the same rapid style, and there were two people on the panel—one with video on and one without. Then they surprised me by asking me to share my screen and open a Java compiler to write a Java program, even though my background and resume indicated work focused on JavaScript rather than Java. To be fair, one of the interviewers handled it more sensibly with follow-up questions, but the whole moment felt off-balance.
11 months ago
Average Positive Bangalore Rural
I went through a structured automation testing flow that started with an actual assessment rather than just a conversation. After the initial screen, …
12 months ago
Easy Neutral Bengaluru
My recruiter outreach moved fast and the whole thing felt tightly scheduled. It started with HR contact and then I had a couple of quick virtual steps…
> 1 year
Average Positive Pune
My interview experience started with a recruiter conversation and then moved into two rounds that were pretty aligned with the day-to-day of QA engine…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process is generally quick and well-organized, often completed within a week, with multiple rounds scheduled tightly and little waiting time between stages. Candidates should be prepared for a fast-paced process that emphasizes urgency around start dates.
TimelineSchedulingEfficiency
Technical Rounds Focus
Candidates can expect a mix of technical assessments that include core QA topics, automation tools like Selenium, and practical coding questions, often with a strong emphasis on real-world application and problem-solving in automation and API testing.
AutomationSeleniumAPI Testing
Behavioral & HR Interaction
The HR discussions can vary significantly in tone and professionalism, with some candidates reporting confrontational or unprofessional behavior, while others found the HR interactions straightforward and supportive. Candidates should be prepared for varying experiences.
HR InteractionProfessionalismBehavioral
Interview Experience & Atmosphere
The overall atmosphere of interviews can differ, with some candidates feeling a supportive environment while others experienced a more aggressive or critical approach from interviewers, impacting their confidence and comfort during discussions.
Interview AtmosphereSupportiveCritical
Post-Interview Communication
Post-interview communication can be inconsistent, with reports of delays in receiving offer letters or updates, leading to frustration among candidates. It's advisable to follow up proactively if there are long gaps in communication.
CommunicationFollow-upDelays
Expectations on Role Alignment
Candidates should be prepared for discussions that align closely with the role's responsibilities, including both automation and manual testing concepts, as well as practical scenarios related to defect management and workflow processes.