Coupa Software Inc Test Automation Engineer Interview Questions
& Process

The interview process was really long, spanning months with multiple rounds. The interviewers were all great, patient, and allowed ample time for answers, fostering two-way communication. Questions were mostly scenario-based and analytical, all conducted over Zoom. While individual rounds weren't overly difficult, the cumulative effect made it tough. It started with an Interview Mocha written test: 3 medium coding questions in 1 hour and 15 easy MCQs on aptitude and testing in 15 mins. Then, there were rounds with the Hiring Manager and Senior SDET (discussing frameworks and Java, with coding), Dev Lead and QA Manager (SQL, performance, and automation), Sr QA Manager (CV deep dive, automation, performance, DBs), Director (CV deep dive, behavioral, assessments), QA Manager (coding, string pattern, data structures, algo), VP (projects, past companies, behavioral/situational), and finally EVP (similar to VP). This 8-round process took about 2.5 months. HR communicated clearance but mentioned org changes due to COVID might delay the offer. A month later, HR offered a role in Coupa, Pune, requiring relocation, which I accepted, leading to another HM interview there. Ultimately, I didn't get the original position, and the Director confirmed I didn't clear, with the original role no longer available. They suggested considering my profile for future openings. It was disappointing, especially during the pandemic peak, but they were professional in communicating the outcome via Zoom.

The interview process started with an online assessment that had 3 coding questions and took 60 minutes, along with 8 MCQs on Aptitude that took 15 minutes. After clearing that, a video interview was scheduled. The coding questions in the assessment were of average difficulty; anyone with coding experience should be able to solve them, especially with 60 minutes for 3 questions. The main challenge was understanding the lengthy question descriptions, which turned out to be simple loop and condition problems once understood. The 8 MCQs were enjoyable and not difficult, with maybe one or two tricky ones involving proportions and sentence restructuring. The actual interview questions were simple and similar to what others have shared. However, the interviewer seemed rushed and tried to make me feel inferior. While polite and attentive, they expected immediate answers, which isn't realistic. I reached the expected scenario in about 5 minutes. In a coding situation, even after solving 5 scenarios, the interviewer was unhappy that I didn't solve the 6th one, which I would have if not interrupted. Although I was rejected, I would happily reject them permanently.

I had my interview at the Pune office in July 2019. The team was really nice and I was even talking to them before the interview. They seemed more interested in my process and approach rather than just right or wrong answers. There weren't really set stages, but rather different interviews focusing on specific areas. The first interview was about databases, the second about test and test automation strategy, and the third about UI automation. There was also an interview to see if I would fit in with the team. They asked me basic questions and gave me a few scenarios to see how I'd handle them. I got selected, but the salary they offered wasn't very high.