EPAM India QA Automation Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for QA Automation Engineer at EPAM India, newest first and distilled into what to expect across the loop.
Get your personalized EPAM India QA Automation Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process started with a recruiter call that went well, but the real drag was everything after that. I waited about two weeks without any update, then I followed up by email and also messaged on LinkedIn. A week later I finally got a response that the recruiter was waiting on feedback from the hiring team. I followed up again about another week after that, and only then did they schedule the technical interview—almost a month after the initial call.
The technical interview covered a wide spread: Java and Selenium showed up a lot, along with REST Assured and API testing. They also discussed testing strategy. I was asked about Cypress, Git, SQL, and SOLID principles, and the session included TestNG and Cucumber as well as two practical coding exercises. Honestly, what threw me off most was how heavily the interview leaned into advanced Java topics even though my recent practical Java background wasn’t in the “freshly daily” range.
2 months ago
Average Positive Singapore
The flow of the process felt structured from the start: the HR team arranged a first technical round that was expected to last around two hours. I knew that if I cleared that, I would move into another round, and then there would be additional client rounds. The overall expectation was that I could answer questions using tools in day-to-day work—because if I hadn’t touched them in a while, I would need to revisit the basics.
When I went through it, the experience itself was positive and professional. The conversation felt engaging, and the questions were relevant to the role and what the team was looking for. What stood out to me was how clear the process felt while I was in it, and that I received straightforward information about the job and team. It didn’t feel chaotic or adversarial; it felt organized and easy to follow.
5 months ago
Average Positive Bangalore Rural
My interview experience moved through two technical rounds and then ended with HR. In the technical parts, the first round was focused on fundamentals…
6 months ago
Difficult Positive Mumbai
After an initial technical step that lasted close to two hours, my interview moved into a managerial discussion and then an HR round. The first techni…
8 months ago
Difficult Positive Raleigh, NC
The interview was tough in a way that still felt intellectually fair, and it ran close to about two hours for the technical portion. They pushed me th…
Unlock every QA Automation Engineer interview experience
