The interview process consisted of an initial phone screen by a recruiter, followed by three additional 45-minute phone interviews with project and team leads.

I was not interviewing for a strictly coding-focused position, but rather for a grey-box or black-box testing role. Therefore, the questions I was asked were typically general inquiries about testing a hypothetical product.

However, I did encounter a few basic coding questions designed to assess familiarity with certain data structures (hash maps, arrays, sorted heaps) and the ability to analyze runtime (Big-O notation).

Most of the questions were things like, "You work for a company that manufactures blenders. How do you test this blender?"

They're basically looking for you to consider every possible angle in which you would test this product:

• Who's the user?
• What's your company's warranty?
• How does it handle standard products?
• How well does it make a milkshake?
• How does it handle rocks if you put them in there? Should it handle rocks?

They also asked me to test an office printer, an ATM machine, and a web browser.

The coding questions I was asked were things like, "Given an unsorted array with n elements where every element except for one is duplicated in the array, how do you find the unique element?"