Pocket Gems Qa Engineer Interview Questions
& Process

I first talked to an HR person by email, and then had two phone screens back-to-back. After that, I went to the office for in-person interviews. For about 3-4 hours, I met with pretty much a dozen people who were all related to the job I applied for. On the plus side, the phone interviews were quick and nice. Waiting for the in-person interviews wasn't long, and they had a room set up just for me, with snacks. The managers and people working on the product asked good, interesting questions. But, a lot of the interviewers were developers who don't interview much. Their questions were sometimes unclear and they seemed a bit awkward. Because there were so many interviewers, the same questions got asked over and over. Also, being a series of separate interviews, the in-person part took longer and wasn't as in-depth as it could have been if it were a group interview.

Applied online and heard back pretty fast from a recruiter. They wanted to set up a phone interview with someone from the QA team. The recruiter said to play the game I'd be working on because they'd ask about it in the phone interview. The person who interviewed me seemed like they were just reading questions off a list and didn't really react much to my answers, which I thought was odd for a phone interview – it should be more of a back-and-forth conversation. I got a generic rejection email later with no specific feedback, and they haven't responded to my request for more details.

The interview process moved along really fast. I only made it to the second stage of testing. The first stage was a phone call to get to know me. The person I spoke with was super nice and seemed genuinely interested in what I was looking for in a job. They really care about fitting into the company culture and emphasize getting along well with others. The second stage was also a phone call with a QA Lead. They asked basic questions about QA policies and techniques. It's important to know more than just the fundamentals of testing; they want to see that you understand the entire QA process so you can contribute at a higher level. That second part went pretty well.