I went through a four-round interview sequence that was fully technical. The early part focused on fundamentals around Java and common QA tooling concepts—things like Selenium and REST-style services—before moving into questions that required more hands-on Java coding. I had to not only write or reason about code, but also explain expected behavior based on the code itself.
By the time I reached the later technical round(s), the difficulty had increased into something that felt genuinely challenging for me rather than just theoretical. I remember it as a tight, knowledge-and-implementation style set of interviews rather than a broad role discussion.
> 1 year
Average Negative United States
The process I experienced was multi-round and drawn out, and the scheduling felt wasteful. I interviewed across six rounds overall, and at first it felt like things were going smoothly—every round was getting scheduled and completed professionally. But what stuck with me was how the last step changed late in the game: the final management round got scheduled with very little time, and the person showed up and concluded I wasn’t a fit. It made me wonder why earlier interviews were run at all when the final decision seemed to land with that last manager.
In another stretch with four technical rounds, it also felt like the company didn’t respect candidate timing. I went through multiple interviews on different days for about an hour each, and after that I expected a response. Follow-ups didn’t lead anywhere, and I never heard back even though the recruiter told me to wait only a couple of days. The whole experience left me feeling like they weren’t organized enough to handle the process responsibly, because “no” would’ve been clearer than extended silence after multiple rounds.
> 1 year
Average Negative Hyderābād
My interview journey stretched over a long period—about 2.5 months—and it ended up being eight rounds. Most of it took place over Zoom, and while each…
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 typically consists of multiple rounds, often spanning several weeks to months, with candidates experiencing anywhere from four to eight rounds. Scheduling can be inconsistent, leading to frustration due to long gaps between interviews and a lack of timely feedback.
Multi-roundSchedulingTimeline
Technical Focus & Coding Rounds
Candidates can expect a strong emphasis on technical skills throughout the interview process, with multiple rounds dedicated to coding, particularly in languages like Python and Java, as well as QA tools such as Selenium. The coding assessments often include scenario-based questions that require careful reading and understanding.
CodingPythonJava
Behavioral & Situational Questions
Later rounds often incorporate behavioral and situational questions that probe deeper into candidates' experiences and thought processes, requiring them to articulate their past work and decision-making strategies.
BehavioralSituationalSTAR
Pressure & Interview Dynamics
Candidates have reported experiencing a high-pressure environment during interviews, with some interviewers seeming rushed or interruptive, which can hinder the flow of conversation and create discomfort.
PressureDynamicInterruptions
Feedback & Closure
Many candidates expressed dissatisfaction with the lack of meaningful feedback or closure after the interview process, often receiving rejections without clear reasons or follow-up discussions, leaving them feeling frustrated.
FeedbackClosureRejection
Assessment Format
The initial assessment typically includes a mix of coding questions and aptitude tests, often conducted online, which can set the tone for the rest of the interview process. Candidates should prepare for a variety of question types and formats.