
Motive Qa Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Motive.
QA Engineer
The whole interview thing at Motive took me about a month and a half. I had to go through 5 stages: first, there was an online test, then a chat with HR, followed by a round with the manager and a coding challenge. The last round, round 5, was a panel interview with 4 people. Interestingly, in the final round, I spoke with the manager, but he didn't ask me to code anything or throw any tech questions my way. Still, I got rejected there. What can you do!
- Tell me about your coding experience.
- What do you know about Selenium?
- Can you discuss your database knowledge?
Software QA Engineer
So I had a really bad experience with this company. It started with an HR call and then went into three interview rounds. The first round was with the Hiring Manager for about an hour, mainly covering the role and asking me to talk about myself. Then, there was a huge second round with five people, lasting two hours, where they asked a bunch of technical and non-technical questions. The third round was with the Senior Manager or Director, focused on cultural fit. The interviewers themselves were nice and knew their stuff, but the HR and recruitment team were completely incompetent. I got no feedback or updates after any round and had to chase them myself. Even after the third round, I got an email from a background check company without being told I'd even passed the interviews. After I submitted my background check info, I had to ask for updates again and send my salary slips. Then, more silence for a few days, followed by a generic rejection email. So, three interviews with seven people over a month, plus background checks and submitting salary details, and they couldn't even be bothered to call with feedback. Honestly, avoid this company, especially their HR.
No confirmed questions were included in this interview report.
QA Engineer
It started with a technical recruiter call, just some basic questions about my current job and the company. Then I had a phone interview with the Engineering Manager where we talked about testing. The third round was also a telephonic with the Engineering Manager, and they gave me a scenario and asked me to write pseudo-code for automation testing. After that, it was an onsite interview with 6 people. That included logical questions about coding for scenarios, writing automation test cases on a laptop, GIT questions, basic coding with unit tests, and discussions with the Engineering Manager about my past experience, the role, and how to improve their current processes.
- Simple Coding questions.
- Questions on GIT.
- Questions on Unit Testing.
Motive Qa Engineer Interview Questions
Quoted word for word from Motive interview reports.
“Reverse an array or string.”
Read reports →“What is the difference between driver.quit and driver.close()?”
Read reports →“What do 5xx codes signify?”
Read reports →“What do 4xx codes signify?”
Read reports →“What is a Put request?”
Read report →“What are the various API error codes?”
Read report →“Can you explain the difference between REST API and Web services?”
Read report →“Regarding automation, what's the difference between implicit and explicit wait?”
Read report →“Can you list some API response codes?”
Read report →Formats, difficulty and experience
Across all 8 Motive interview reports.