Real, anonymous reports from people who interviewed for QA Automation Engineer at Coforge, newest first and distilled into what to expect across the loop.
Get your personalized Coforge 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 Coforge interview journey followed a pretty typical structure, and I could tell they were leaning hard into hands-on automation and testing fundamentals. First I had a screening-style technical start where I was asked basic Java topics like arrays and strings and to code small logic, then move into Selenium—specifically locating an element using an XPath and working through scenarios like handling multiple windows. They also asked about APIs (REST and SOAP), and they probed my understanding of status codes. To wrap it up, I got Rest Assured questions as well.
After that, the process felt aligned with an expanded “engineering scope” rather than only UI testing. I remember the conversation touching multiple areas like ETL and SQL concepts alongside Python and GCP, plus scenario-based problem solving and automation testing discussions. There were also behavioral and role fit questions that came after the technical portion.
> 1 year
Difficult Neutral Noida
From the moment I got scheduled, the process felt both deliberate and a bit slow. It took about a month end to end, and I ended up in four video-based rounds that included a client discussion. The overall vibe was mostly smooth, and the questions stayed in the technical lane and then expanded into the later discussions.
Across the stages, I felt like interviewers were actively pulling from what they had in front of them and asking a lot of direct questions that matched common testing and development topics. It didn’t feel like there was a lot of fluff—just lots of thorough coverage—though there were a few moments where a question seemed a little off from the point.
> 1 year
Average Negative Bengaluru
I walked into the Coforge process expecting a normal exchange—background questions to anchor the role fit, then structured assessment—but that’s not h…
> 1 year
Average Positive Pune
My process started with a simple three-round sequence: a technical round, then a technical-managerial round, and finally an HR round. The structure wa…
> 1 year
Difficult Positive New Delhi
The interview felt good, but it was still genuinely challenging. A lot of the questions followed familiar patterns—similar to common practice problems…
Unlock every QA Automation Engineer interview experience
