My journey started with a recruiter interaction and then moved into a couple of internally technical steps. First came an internal technical round where I got asked scenario-heavy questions and had to talk through how I’d work in an agile environment. I was also questioned on testing execution thinking—like estimating how long it would take to execute about 50 test cases—and I had to explain things like the bug life cycle. Requirement handling came up too, including what I would do when a requirement document was shared, and I even got asked about a Java program.
After that, I had another technical discussion that was more in-depth and more focused on core testing concepts with a strong “go deep” feel. The topics included API testing, manual testing, and Selenium, plus Rest Assured in depth. I also had to write out code for a small reverse-string style problem, which made the interview feel more practical than purely conceptual.
10 months ago
Difficult Positive Hyderābād
I went through a structured, multi-round interview that felt pretty standard in format but still demanding in execution. Before I was even fully shortlisted, I was asked to create a sample framework on their testing website, which set the tone early—this wasn’t just a conversation, it was something hands-on.
After that, I ended up with three rounds: a technical round, then an HR round, and finally a client round after the initial rounds cleared. The client stage felt like the last technical checkpoint, and it was paced around approvals and moving forward once that fit was confirmed. Even though the overall process went according to the schedule they laid out, it still carried a “try your best to crack it” difficulty, with the outcome depending on how the interviewer assessed both knowledge and fit.
> 1 year
Average Positive Hyderābād
After I got into the interview, most of it was centered on my project work and the core testing stack I’d listed. I had an initial technical discussio…
> 1 year
Average Positive Hyderābād
I went through a multi-level interview that was pretty focused on evaluating technical strength and then pairing it with process and leadership expect…
> 1 year
Easy Positive Hyderābād
My interview felt fairly smooth and mostly matched what I had on my resume. The questions started in a manual-testing and API/automation basics space,…
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 consists of multiple rounds, including technical discussions, manager-level evaluations, and HR conversations, often culminating in a client round. Candidates should expect a structured format with a clear progression through these stages.
Multi-roundTechnicalHR
Technical Depth & Practical Skills
Candidates will face in-depth technical questions focused on core testing concepts, including manual testing, API testing, and automation tools like Selenium and Rest Assured. Practical coding exercises and scenario-based questions are common, emphasizing the application of knowledge rather than just theoretical understanding.
Core testingSeleniumPractical coding
Behavioral & Process Discussions
Interviews include discussions around project experience, agile methodologies, and testing processes, often requiring candidates to explain how they would handle specific scenarios. The emphasis is on understanding candidates' thought processes and alignment with the company's operational expectations.
BehavioralAgileScenario-based
Communication & HR Interaction
HR interactions are generally positive and involve regular updates, although some candidates experienced delays and miscommunication. The HR round typically focuses on logistics like salary and location after the technical evaluations.
HR communicationLogisticsUpdates
Difficulty Level & Expectations
The overall difficulty of the interview process is perceived as high, requiring solid foundational knowledge and the ability to think critically under pressure. Candidates should prepare for a rigorous evaluation that tests both technical skills and cultural fit.
DifficultyFoundational knowledgeCritical thinking
Feedback & Outcome Variability
Candidates reported mixed experiences regarding feedback and outcomes, with some feeling misled about their progress after initial positive interactions. The final decisions can vary significantly, leading to frustrations when expectations are not met.