Expedia Product Manager Interview Questions & Reviews

Interview Details – great hiring process- very thorough and extensive process. everyone was incredibly social and friendly and the questions were quite challenging. recommend preparing carefully for this. interview was over 2 days with about 8 people. found this based on a referral from a friend and a phone screen by a recruiter.

Interview Details – The hiring process is like anywhere else.
You initially talk to the recruiter, who will ask you very broad set of questions like "Why Expedia?" or "Tell me about your background". You will also get a little bit of an insight on the job itself.
My second interview was with a director of the department, who the position wold answer to. The manager sounded very strict and in a way, unpleasant to speak with. The manager wanted to know my experience with Agile/Scrum, which I had little of, so the manager asked me to do homework before asking me to come in for an internal interview process.
Questions were related to Expedia's website, like "What would you change on a specific portion of the website?", "Write user stories for the proposed changes.", and "Given a team developing a front end of the application, and a team developing a back end application, tell me how you would create a roadmap for the project, and develop a schedule." - Pretty basic stuff for the PM work that would be relevant.
After I turned the homework in, I was asked to come in for a day of interviews. The internal process was with 5 people, some interviews being in an hour range, and a few in half hour range.
Pre Interview. Meet with the recruiter and she takes you to your interview room. Not really an interview.
Interview 1.Meet with the Sr.PM and have a lunch interview. Great insight on what the team is developing and questions like, "How would you as a PM track what your a client selected in their itinerary?"
Interview 2. Another interview with Sr.PM. More of questions about the internal structure of the team and what everyone does. A few questions mainly about my past work. Know your resume' well.
Interview 3. Sr. Developer came in, which surprised me, since I'm not technical in development. He looked very tired and not very avid about the interview process. He explained that there will be no code questions, but wanted to find out if I could, as a PM, explain things to him from a technical perspective. I was a bit too high-level for him. Questions asked were like "Explain web services to me?", and "How does a web request works?". When it was my turn to ask questions, he was picking his nose, rubbing his face and barely sitting on the chair, with his eyes barely open, which was unprofessional.
Interview 4. Meet with peer PM. The guy was very active, involved and friendly. Really wanted to know about my past, and told me about his line of work, which was very interesting. Asked me questions like "How would you keep your developers active and engaged?", and questions about my past experience. I finished this interview feeling great and energized.
Interview 5. Meet with your future manager. This was the same manager that gave me homework. The manager was somewhat arrogant and not overly friendly. This might be expected from someone,who you might answer to in the future. Asked me quickly about how my day has gone so far, and quickly dove into questions not related to PM work, but mainly about the back end of the Expedia website, which I knew pretty much nothing about. Questions like "Explain how an object is passed to the results page and what is included". Asked to clarify, which only frustrated the manager. My answers from the beginning seemed to not be good enough for the manager, and after the discussions on the answer, which the manager felt like having to chew out for me, I felt like I did not successfully go through that portion.
I made sure to say in my closing statement that it is more important for me to know they pick the right candidate, and if it is not me, I understand. I do not think the manager liked this one bit.
Overall, great day full of great people. Wish I was more prepared for the wrath of the manager.

Interview Details – Ask about "if you know the user average stay on a page for 5-6 second" what additional data you would need to justify the "5-6 second " is good or bad?

Interview Details – Phone interview was about 30 minutes long. Talked about resume and why the switch from Dev to Product Manager.

Interview Details – Had a brief phone screening with the HR recruiter. I was later called for a 1:1 interview with a member of the hiring team. The interviewer did not seem to be prepared, she just let me do most of the talking and only asked questions based on what I was saying, mostly clarification questions. The conversation took almost 45 minutes. No real feedback was received, only that they decided to go with an internal candidate. Not sure what the reall reason was, this seems like a standard response when they're not interested.

Interview Details – I wouldnt say it was easy. The questions were very straight forward. But the tricky part was the expression on the interviewers faces. Wow! You couldnt tel if they were impressed or not. After the interview I felt I could have done better.

Interview Details – The HR contacted for a phone interview and decided on day and time . The interviewer was a Senior product manager. After interview when asked about feedback , he was polite and explained the good and negative points