I went through a campus-style drive for a QA intern and honestly the whole thing felt chaotic from the start. It started with a recruiter-style call, and then the next steps didn’t line up with what was promised. The process dragged on in a way that made me feel like I’d essentially lost an entire day.
After I cleared my first round, the second round was confusing: I was told to connect later, but then there was no follow-up for a long time. It wasn’t just me—more than half of the candidates ended up getting left hanging after being asked to connect virtually, and some people were even told to leave the premises for the next step and then never heard back.
9 months ago
Average Neutral Noida
My process started with a technical screening on HackerRank. That first round was hands-on and coding-focused, and after clearing it I moved to a more direct conversation with a manager. In that one-on-one, I was given a DSA-style problem and then shifted into some basic HR questions afterward.
Across the journey, I felt the technical evaluation leaned heavily on coding and core testing skills rather than vague theory. One version of the technical portion included problem-solving plus Python-specific work and testing concepts—things like lambda functions and Pytest usage, including how to structure tests and use markers. I also had to deal with broader fundamentals like directory structure and file significance, not just the “write code” part.
> 1 year
Difficult Positive India
I ended up going through a pretty structured, multi-round QA hiring flow. First there was an online assessment meant to check general aptitude and pro…
> 1 year
Easy Negative Bengaluru
My first HR touchpoint set expectations clearly: I was told there would be four rounds total, and the flow would start with a tech round. The first te…
> 1 year
Difficult Positive Noida
I had a straightforward but challenging interview sequence for a QA engineer role. The first round was Java plus Selenium, and it required more than s…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically consists of multiple rounds, often starting with an online assessment followed by technical interviews and an HR discussion. Candidates noted variations in structure, with some experiencing clear and coherent flows while others felt the process was chaotic and poorly managed.
multi-roundonline assessmentHR discussion
Technical Evaluation Focus
Technical interviews emphasize a mix of coding skills, testing fundamentals, and practical problem-solving, often incorporating languages like Java and tools such as Selenium. Candidates should be prepared for a range of topics, including DSA, frameworks, and API testing.
JavaSeleniumDSA
Behavioral & Managerial Rounds
The final stages often include behavioral or managerial discussions focusing on project experience, team dynamics, and communication skills. Candidates should be ready to articulate their experiences and how they align with the company's collaborative culture.
behavioralteam dynamicscommunication
Difficulty & Candidate Experience
Overall difficulty levels vary from easy to challenging, with some candidates feeling that the interviews were straightforward while others found them intense and demanding. Experiences can differ significantly based on the interviewer's style and expectations.
difficultyintensityinterviewer style
Communication & Follow-Up
Candidates reported mixed experiences regarding communication throughout the process, with some feeling well-informed while others faced delays and confusion about next steps. Clear communication from recruiters is crucial for a positive experience.
communicationfollow-upclarity
Preparation Insights
Candidates reflected on the importance of being well-prepared across various topics, including coding, testing methodologies, and situational responses. Practicing problem-solving and understanding the role's requirements can enhance performance.