EPAM India QA Automation Engineer interview: technical breadth and delays

EPAM India·QA Automation Engineer·Reported Jul 2026
Technical ScreenIn progressEasy

The recruiter call went well. After that, though, the process became a long wait. I heard nothing for about two weeks, followed up by email and LinkedIn, then waited another week for a reply saying the recruiter was waiting on the hiring team. I followed up again about a week later, and the technical interview was finally scheduled almost a month after the first call.

That interview covered Java and Selenium heavily, as well as REST Assured, API testing, testing strategy, Cypress, Git, SQL, SOLID, TestNG, and Cucumber. There were two practical coding exercises. What threw me was the emphasis on advanced Java when my recent hands-on Java work was not something I was doing every day.

I tried to get feedback afterward, but the silence continued. More than two weeks after my follow-up, and over three weeks after the interview, I still had no final decision. The technical conversation was worthwhile, but the repeated chasing and slow communication took over the experience. I left disappointed.

Location: Spain. Overall feedback: negative. Offer status: no offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
EPAM India
Role
QA Automation Engineer
Rounds
Technical Screen
Outcome
In progress
Difficulty
Easy
Date
Reported Jul 2026

Real EPAM India interview experiences

First-hand reports from EPAM India candidates — the rounds, the questions they were asked, and how it went.

All 8 EPAM India interview experiences