Expedia Group Interview Questions
& Process

Expedia always uses HireVue for the first interview round, no matter the role. HireVue is a pretty bad way to assess candidates. It requires a lot of effort from candidates for a one-way conversation, and there's no guarantee that anyone will even watch the responses. Many good candidates just aren't good at HireVue because it's a one-way conversation. Some people do well in a live interview but can't get past HireVue. This means Expedia misses out on a lot of potential hires. Also, some strong candidates won't even do a HireVue interview because the time it takes to prepare isn't worth the level of consideration they're getting. Looking back, I should have avoided it too. There have also been big lawsuits against HireVue for unconscious bias and discrimination. When Expedia uses HireVue for the first round, they risk continuing these biases and not having an inclusive hiring process. Anything they do later to make sure everyone is considered fairly is pointless if HireVue has already filtered out a lot of people because of AI bias. Basically, if Expedia keeps using HireVue, I'll probably just avoid them.

I had a 4-video call interview process, in English, with people from 4 different countries. The first interview was with the recruiter for classic pre-selection questions. The second was with my future manager about my professional experience. The third and fourth interviews were with a senior manager and a transverse manager, where they asked quite technical questions about my experience for the position and concrete cases I've lived through. I received a motivated negative response about 2 weeks later. All my interviewers were very nice and made me feel comfortable. The recruiter in charge of my application was available and friendly.

So, the interview process started with a Hackerrank test that had 2 easy-medium DSA questions. Then there were 3 more rounds focusing on DSA, each with 2 medium DSA questions. After that, I had a Hiring Manager Round where we mostly talked about my resume projects and some situations from my current job. The last round was an LLD round. They asked about LRU Cache, but it was more than just solving it like on Leetcode; they wanted me to think about the design in terms of things like concurrency, scale, resilience, and idempotency. I didn't get the offer in the end, but the HR actually gave me feedback over the phone, which was pretty cool compared to other companies that just ghost you.

I had a screening call initially where the HR asked about my previous experiences and explained the role. The nature of the role sounded more like an end to end ML Engineer rather than an ML Scientist. The interview process consisted of a live coding round and intense loop interviews following that. I liked the coding round as it was similar to real world problems rather than leetcode style. The loop interview questions were not difficult but I was quite surprised as two of the interviewers asked me the same questions in the same order almost as if reading from a script. The interviews strictly focused on theoretical knowledge rather than practical or past experiences which made it harder to demonstrate skills and experiences beyond theory. I received a rejection call which could have been an email.