I had an online interview that felt pretty straightforward and easy compared to what I’d heard. The main part was a coding-style question that involved stack/dynamic-programming concepts, and I was asked about things like the next greater element and a buy-and-sell stocks problem.
After that, the conversation shifted into a discussion about my project. I talked through how I approached the testing and what I did to verify things, and that became the tone for the rest of the call. It wasn’t stressful, and overall it felt like a smooth chat focused on fundamentals and my own experience.
8 months ago
Average Neutral Hyderābād
My process started with multiple coding rounds before I ever got into deeper conversation. I went through three coding-test rounds, followed by two additional online coding rounds with technical recruiters, and then ended with an onsite interview at their office.
The first part was pretty easy, but the second round stood out because the interviewer didn’t seem familiar with QA specifics. The questions still felt related to the general technical space, but there was a noticeable mismatch in how QA-focused the discussion was, and it threw me off a bit because I was expecting clearer QA depth.
9 months ago
I took the ServiceNow QA Intern online assessment expecting something light, almost like it would be more introductory. I thought it might be the kind…
> 1 year
Average Negative India
I went through a multi-stage technical process that was very coding-heavy in tone even though it was framed for QA. In the first tech round, the split…
> 1 year
Average Neutral Bengaluru
I attended two rounds for the role. The first round was one technical checkpoint, and then the second round was where things ended up feeling confusin…
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 coding assessments, technical interviews, and an HR round, often spanning one to two weeks. Candidates can expect a mix of technical questions related to QA and coding, with some reports indicating a focus on Java and data structures.
Multi-roundTechnical interviewsHR round
Technical & Coding Focus
Candidates should prepare for a heavy emphasis on coding and technical questions, including data structures, algorithms, and Java-specific topics. The coding rounds may vary in difficulty, with some candidates reporting a noticeable increase in challenge during later rounds.
Data structuresJavaCoding challenges
Assessment Expectations
Initial assessments can be more challenging than anticipated, often including problem-solving and testing questions that require a solid understanding of QA concepts. Candidates should be prepared for a rigorous evaluation that goes beyond basic definitions.
Online assessmentProblem-solvingQA concepts
Behavioral & Communication Aspects
Behavioral questions are integrated into the interviews, often focusing on teamwork and project experiences. Candidates should be ready to discuss their approach to testing and how they communicate within a team context.
Behavioral questionsTeamworkProject discussion
Interview Atmosphere & Professionalism
The atmosphere of interviews can vary significantly, with some candidates reporting unprofessional interactions or abrupt shifts in focus during discussions. It's important to remain adaptable and maintain professionalism throughout the process.
ProfessionalismInterview atmosphereAdaptability
Feedback & Outcome Clarity
Candidates often report a lack of clarity regarding feedback and outcomes, with some feeling surprised by rejections despite positive interactions. Following up for feedback may not always yield responses, so candidates should manage expectations.