I applied online. The process took 2 months. I interviewed at Expedia Group (Austin, TX) in May 2022
Interview
4 rounds. 1 OA, 1 Leetcode style round with 2 questions, 1 System Design and 1 Behavioral.
Leetcode style round had 2 Medium questions.
System Design round had 2 questions.
Behavioral was with HM.
Other Software Engineer II interview reviews for Expedia Group
I applied online. I interviewed at Expedia Group (Seattle, WA) in Apr 2026
Interview
The process consisted of two main stages:
Coding Round (HackerRank)
I completed two coding problems on HackerRank. The questions were in the easy to medium range and focused on problem-solving, data structures, and basic algorithmic thinking.
System Design Round
This was a discussion-based round where I was asked to design a URL shortener system (similar to TinyURL). The focus was on high-level design, scalability considerations, API design, and handling tradeoffs.
Overall, the difficulty level was moderate, with more emphasis on clarity of thought and structured problem-solving rather than highly complex algorithms.
I applied through an employee referral. The process took 1 week. I interviewed at Expedia Group in Mar 2026
Interview
It is a phone interview. We introduce each other. We talked about some basics on my resume. I was asked from some general why choose Expedia, and some SDE fundamental questions.
I applied online. The process took 2 months. I interviewed at Expedia Group (London, England) in Nov 2025
Interview
Applied online at the start of October and accepted an offer at the start of December. Interview process consists of a HR screening, an informal technical interview with a manager, then the 'loop' which consists of an hour each of a live coding exercise, systems design and behavioural on different days. At each stage interviewers were really friendly and gave a relaxed vibe. After the final interview they took about a week to reply with an offer. Live coding was similar to a real problem you might solve at Expedia rather than a Leetcode question which I appreciated a lot, with some discussion around complexity at the end.