Real, anonymous reports from people who interviewed for QA Engineer at Phonepe, newest first and distilled into what to expect across the loop.
After a recruiter touchpoint, I moved into a short sequence that felt pretty straightforward but still tested whether I could code cleanly and troubleshoot. The next two rounds were mostly DSA-focused: I was asked two problems, one easy and one medium, and I had to code them and produce the correct output.
My PhonePe QA Engineer process started off fine, but the timeline got frustrating. After I finished round one, HR took about three weeks to come back with the next step. It felt especially wasteful because they were trying to push the remaining rounds into the same week due to internal targets.
The interview process typically consists of four to five rounds, including technical rounds focused on data structures, automation, functional testing, and a managerial discussion. Each round builds on the previous one, assessing different skills relevant to the QA Engineer role.
Candidates can expect a strong emphasis on data structures and algorithms, automation frameworks, and functional testing, with some interviews requiring practical coding and problem-solving skills. The technical rounds often include discussions about past projects and specific testing methodologies.
Many candidates reported delays in communication, particularly after the final rounds, leading to frustration and uncertainty about their status. Feedback can be inconsistent, with some candidates receiving positive reinforcement during interviews but unclear outcomes afterward.
The managerial round tends to shift in tone from technical to more casual discussions about work culture and expectations, which can feel disconnected from the technical evaluations that preceded it. This round can significantly influence the final decision.
Candidates experienced varied timelines, with some facing lengthy waits between rounds and final decisions, which can detract from the overall experience. The process may take several weeks to complete, leading to a sense of lost time.
Several candidates noted a lack of clarity regarding expectations for specific skills, such as Appium or mobile testing, which could lead to misalignment between candidate preparation and interview focus. Clearer communication about required skills upfront could improve the process.