Manhattan Associates Qa Engineer Interview Questions
& Process

Got a call from the Manhattan office for an interview, which was exciting. I went through all the interview rounds: technical, managerial, and HR. After finishing the rounds, I was asked to fill out a form with my details and received a confirmation email about being selected. They requested my salary slips, recent hike letter, and other documents, stating an update in 3 days. I sent the details. After 3 days, I followed up via email and was told they were working on the offer letter and to wait up to 10 days for an update. I waited about 15 days and emailed again for an update. The reply stated that the offer was denied by the business due to internal parameters and they couldn't proceed. This was unexpected from such a well-known company. They took all my information and documents, only to inform me after more than 3 weeks that they wouldn't proceed. The whole experience was very disappointing.

So, first a consultancy reached out about a job change. They asked about my current role and what I'm looking for, then presented this job and set up the interview. The first part was a written test covering Java, QA, Aptitude, and SQL. After that, I had a technical interview focused on Selenium and Java, with a lot of XPATH questions, especially on dynamic properties, and some Java. Then came a managerial round with more SQL and general testing concepts, plus puzzles and Linux. They said puzzles are more about the approach than the exact answer. Finally, there was an HR round to discuss my interest in the company, reasons for leaving my current job, salary expectations, and notice period.

I applied through a staffing agency and interviewed at Manhattan Associates in January 2015. The whole process took about a day and had 3 rounds. First was a written test with manual (18 questions), SQL (11 questions), and QTP (11 questions, but optional). It also included creating test case scenarios and describing bugs from given data. Then, a face-to-face technical interview that was pretty easy. They asked basic questions like drawing the bug lifecycle, the difference between smoke and regression testing, sanity testing, bug vs. defect, priority vs. severity, and how to check if a defect is deferred. There were also SQL queries, including joining two tables and using the LIKE operator.