Unity Software Test Engineer 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.

A recruiter messaged me about interviewing for a software test engineering position in the San Francisco office. The entire process was rather involved - it consisted of several phone screens, a programming assignment which I spent something like 6 hours on, and an ~5hr on site interview. Given this, I find it extremely unprofessional that it's been something like 3 weeks since I interviewed, and I haven't heard anything back from Unity - no offer, no rejection, no updates, nothing. So I hope my experience can be a tale of caution for others who are considering to apply here - think twice before investing a lot of time in a programming test and/or taking a day off of work to interview there.