Friday afternoon 4 pm, a simple talk for an hour. Two newly hired employees talked with me, but only one spoke. And, one of them was different from what I had been told in email. They asked whether I talked with HR. I said no. So she asked how much do you know about AppNeuxs, I tell I reviewed the website and talked about it. I missed something because the different platforms have different functionalities that I could not connect well. What are you doing now in the position? I tell what I do. Tell me a project you are excited about. Tell me something about one of your projects. This took much time because they tried to build a situation in which users are willing to use it. Based on the project, how would you test it? (This is so big question but suitable for any case, I used 3 rounds to narrow down what they were trying to get from me. And they said they did not care about the UI. But how can that be? My project was supposed to be a mobile one, why cannot I test the output in different screen. What if the output is so annoying? And stopped by this, I was not easily guided to the track they want on user cases. There are so many cases I can create based on what I did. I just focused on the text label to create many. If I did not give a big picture of the test, I admitted it. But I never get hint of that. And at 5 pm, I was interrupted again, which was reasonable.) Then What would you see yourself in 5 years? I said something like dive in testing, know more about development cycle, know the things behind the test and find the reasons, understand the great efficiency of the product in AppNexus. When I knew they do not code I thought this is even better because this looks like what I do right now. And then I explained a lot trying to build the connection to the position. They did not know what I am talking about and no more desire to know it. Even though I show all I get, I never saw the question in their minds that "is this a right person". I asked them what the most challenging part is in their work and how they communicate with other groups and within groups (because I read all reviews here and was curious how they handle this), and whether they are responsible for different groups separately. The answers were clear enough. They were just following the routine and asking the questions that can be asked to anyone, pretty much like yeas ago I had a phone interview by an intern in CBOE. I was the lab mouse again I am afraid. Even I try to connect my current position to their position showing that I can be a good fit because I have this this similarities and apparently they did not get it, continuing questions. If I interview a person, I will let know him know this is serious because he prepared for some time so I need to be responsible for him, and then for my team. From this experience, neither.

Phone interview included the introduction of the past work, how do you know AppNexus and why you are interested in this position ( This question is repeated in every step of the interview by everyone - you'd better prepare a good strory ), and how to test a specific object ( you need to consider all of possible input scenery ). Onsite included one non-tech warm-up, three tech interviews and one non-tech with Director and the last with HR. The first two tech interviews were similar, they introduced the business model they used and asked how to test it. The third tech interview was also about algorithm and how to test it, code review of a solution. In sum, all of the testing question need you to answer " what's the possible input? " P.S. the next room also had an interview at the same time, it was about Software Engineering. The code on the board was about consumer and producer, a classic problem in multithreading. Comparing with this question, I can't complain my interview was hard.