PhonePe Test Automation Engineer Interview Questions
& Process

This interview process was quite lengthy. After the first round, it took HR three weeks to inform me about the second round. Despite their need to meet targets, they pressured me to attend subsequent rounds in the same week. While the interviewers were competent, their questions lacked clarity. If they specifically sought candidates experienced in Appium or mobile app testing, this should have been clarified in the initial round, rather than extending the process and wasting everyone's time. Overall, it was an acceptable experience, though time-consuming, and I learned from it.

I went through their whole interview process and was really let down by how it ended. I passed three super technical rounds, all tough and detailed. The interviewers in those rounds really got my skills and picked me for each stage, making me feel like my abilities were being judged right. After that, I had a managerial round, which wasn't technical at all. I'm still not sure if I was rejected in this last round or later. If this stage was the reason for rejection, it makes me wonder: were the three technical rounds not enough to confirm my skills? Since I would have worked closely with the technical team who already approved me, why should a non-technical manager's chat matter more than their assessments? To top it off, communication was slow. After all four rounds, I heard nothing for over a week. Only when I chased HR myself did I get a rejection email the same day. The lack of clear communication, the delay, and no useful feedback made the whole thing feel unprofessional and discouraging.

The interview process for the SDET role had 3 rounds and was medium difficulty. They focused on DSA, Test Engineering, and resume discussion. Round 1 was a DSA problem-solving round, either online or technical coding, with easy to medium difficulty. Round 2 was also DSA focused with an experience-based discussion. It had 2 DSA questions and a discussion about past projects, including the test automation framework used, tools/languages for daily work, handling flaky tests/CI/CD issues, and integration with reporting/test management tools. Round 3 was an HR + Managerial round. It covered behavioral and technical topics, with a deep dive into past experience from the resume. They asked about performance testing tools (JMeter, LoadRunner), writing/reviewing test plans, creating effective and edge-case test cases, handling late-cycle bugs, prioritizing under deadlines, and collaborating with developers/product owners. The manager's tone was friendly but focused, assessing both technical understanding and communication. Overall, it was a well-rounded process emphasizing DSA and problem-solving initially, then moving to real-world SDET tasks. Being confident in coding and QA was key.