The interviews consisted of 2 phone screens and an onsite interview.

The first phone screen was with the manager of the group and focused on my experiences and some technical questions, e.g., "How would you approach testing an elevator?" Hint: First, list the types of test plans you will need to write, and only then specific tests.

The second phone screen was with one of the senior team members. It was similar to the first one but more relaxed.

After completing the phone cycle, I received an email from the recruiter inviting me for an in-person interview.

My interview, from what I heard, was not typical. It started at 9 AM and lasted until 5 PM. I met 6 interviewers:

• Several Senior Test leads
• Development leads
• Developers
• Testers

Most interviews included an "HR component" or general questions about testing and coding, with questions such as:

• If you have a conflict with your subordinate, how would you resolve it?
• If your product has 6 features, but your team has time to test only 5, how would you choose which one to exclude?

Core coding questions were fairly expected and easy. The language of choice did not matter, as long as you could write pseudocode.

Check if Tic-Tac-Toe has a winner.

Delete the n-th element from a linked list. Note: you do not have a pointer to the head of the list.