
Coforge Test Automation Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Coforge.
QA Automation Engineer
So the interview process usually has a few steps. First, a recruiter calls you to chat about your background and skills. Then, there's a technical interview where they might ask you coding, automation, or testing questions. If that goes well, you'll probably talk to a panel or the hiring manager about problem-solving, frameworks, and stuff you've done before. Some places give you a take-home assignment or a live coding challenge. Lastly, HR checks if you're a good fit for the team and talks about salary and the role. It could take anywhere from a few days to a few weeks.
- Was the interview sufficient for moving forward?
QA Automation Engineer
I wanted to share my interview experience at Coforge. While I respect the interview process, I felt some parts were unprofessional. Typically, interviews start with basic questions about my background, like name, experience, domain knowledge, and tool/language skills, but these were skipped. Some questions felt random and didn't really test my fit for the job. Also, the interviewer's attitude made it hard to have a constructive conversation. A more structured and respectful chat would have been better.
- What steps would you take to debug a failed test case?
- Could you provide an example to illustrate your explanation?
QA Automation Engineer
An interview was set up via a third party. The first round involved only Java questions and programming tasks, which I passed. I was then scheduled for a second round on Saturday. During this second round, the interviewer was quite rude. They questioned my salary expectations and then asked about database queries, security testing (which I mentioned I hadn't done as it wasn't in the job description), and browser compatibility testing. Interestingly, the interviewer seemed pleased that I lacked deep knowledge in browser compatibility and then argued that automation is too expensive and manual testing should be preferred. I attempted to respond respectfully, but given the situation, I avoided escalating. Overall, the experience was terrible.
- What Java questions do you have?
- Can you write Java programs?
- Could you write database queries?
Coforge Test Automation Engineer Interview Questions
Quoted word for word from Coforge interview reports.
“What's the difference between findElement and findElements?”
Read reports →“On irctc.co.in, how would you search for a train from Delhi to Mumbai?”
Read reports →“Write a Java program to calculate the area of a triangle.”
Read reports →“What does a Client side status code signify?”
Read reports →“What are the different types of XPath?”
Read report →“Could you define Implicit wait?”
Read report →“How would you write a SQL UPDATE query to update a blank employee name in the employee table, using data from another table that contains both employee name and ID?”
Read report →“Can you learn all the concepts in a Java book by heart?”
Read report →“What distinguishes an Interface from an Abstract Class in terms of architecture?”
Read report →Formats, difficulty and experience
Across all 15 Coforge interview reports.