Unity interview questions

-- 45 min., phone interview with the director of QA. -- 1 hour~, "coding exercise" (which is less code and more a process questionnaire). -- 6 hours, on-site panel session and lunch with a few of the employees. Most of the questions throughout the interviews involved testing strategy and process through given scenarios. It was difficult (but not overly so), they asked some in-depth questions on my overall approach to testing as well as specifics on how I would design plans and reports to communicate with managers/supervisors.

5 interviews (2 in person, 3 over video conference). Interviews happened in different days due to my own time availability. 2 interviews were in person and 3 over video (one from home, 2 from the office). The ratio of in-person/remote was due to the current small size of the team I was applying for, and not a general pattern of interviews on Bellevue office. All interviews were deep yet conversational. No confrontational attitude, as I've seen in some other companies. It was a good mix of technical questions, posted as open-ended discussions about the systems at Unity and inquiries about my past experience. I felt that the interviewers got a good understanding of what I'm capable of, without resorting to traditional template-based quizzes or coding questions. Because of that, if felt easier than they actually were. I really enjoyed how the interview was framed - as a free flowing conversation - and I think I had more fun than one would be allowed to have in a interview process :).