On-campus interview that lasted about 25 minutes. Was asked to talk about a few things on my resume, and then to write a code to remove duplicates from an array. Didn't feel very good about the coding session--my answer seemed inefficient. Apparently they agreed that I was better at talking than I was at coding, as they asked me to fly out for the PM role. Once there, I was placed in an interview group of ~20 other candidates. One thing that was strange about our experience was that instead of the typical variable number of interviews, we were all given 4 (and told that we would be). They also guaranteed us results after lunch, which was both a relief and extra stressful. Interview one: we chatted for a while and then talked through a problem regarding system updates and server communication (the keys to this one were asking questions that made clear what each party knew and also understanding the priorities of the different updates). Interview two: My worst interview. Talked about solving Seattle's traffic problems (a "see how you think" kind of problem) and then had a shortest-path algorithm variant. I picked a poor approach for the latter but corrected myself with a simpler and cleaner answer before the interview was over. Interview three: Write an algorithm to solve a NYT-style cryptogram (actually I have no idea if these are real or not--I have never heard of them). Then, design an app. Then, make money off of it (ads don't count). A really fun interview, as he and I kept building off each other's ideas. Interview four: Design a parking lot system (with some additional specifications). The keys were A) to not overcomplicate things, as the users crave simplicity, not technology, and B) to recognize that ultimately the system isn't worth implementing from management's standpoint, since the improvements wouldn't affect productivity. We went to lunch, and then came back to learn our fates!