GeeksforGeeks Question · Jul 2025

Expedia Interview Experience

Question Details

I applied through LinkedIn. Almost, after 1 week I received a Hello From Expedia, It was the link for Online Assessment.Round 0(Online Assessment 1Hr 40Mins): You are g...

Full Details

I applied through LinkedIn. Almost, after 1 week I received a Hello From Expedia, It was the link for Online Assessment. Round 0(Online Assessment 1Hr 40Mins): You are given a vector of strings you are supposed to concatenate their occurrences if they occur more than once.

Example :

Input: [tv, musicPlayer, microwave, tv, mediaPlayer, tv]

Output: [tv, musicPlayer, microwave, tv1, musicPlayer1, tv2]

Solution: Can be easily solved using hashmaps. You are given a Comparator class you need to implement 3 functions, bool compare(int a, int b) bool compare(vector a, vector b) bool compare(string a, string b) You need to implement these functions such that it returns true if both arguments are equal otherwise false. Count the number of ways to divide N in k groups incrementally Round 1(Technical Interview): The Interviewer has 5 years of experience and was very friendly. He introduced himself first and asked me for a quick introduction. Then he jumped into coding questions https://leetcode.com/problems/best-time-to-buy-and-sell-stock/ https://www.geeksforgeeks.org/dsa/find-the-number-of-islands-using-dfs/ I was choked on 1st question for some time but the interviewer gave me some hints, and we solved the question. I did a minor mistake in the 2nd question interviewer pointed out and I fixed that and then the interview ended. Round 2(Technical Interview): The Interviewer has 8.5 years of experience and was very calm. He introduced himself first and asked me for a quick introduction. Then he jumped into coding questions https://www.geeksforgeeks.org/dsa/check-whether-two-strings-are-anagram-of-each-other/ https://www.geeksforgeeks.org/dsa/print-a-given-matrix-in-spiral-form/ I solved both the questions in a very short span of time, then the interviewer asked me some questions on the sorting algorithms. He asked me about the Insertion Sort, Selection Sort, and Merge Sort. And finally, he asked me if I have any questions. Round 3(Hiring Manager): This round was not pre-scheduled, and was scheduled after evaluating my performance in the earlier rounds. The hiring manager was very experienced, 15 years. He asked me a lot of conceptual and theoretical questions. He started with my introduction. Questions asked in the round were: Previous experience, current project, and tech stack I have worked on. Difference between Interface and Abstract class with a real-life example OOPs concepts Deep dive on Inheritance and Polymorphism Why use Cloud Service Features and Benefits of AWS Resiliency in AWS What Platform independence. Why are you looking for a change and why Expedia? The interview lasted long for 1.5 hours.

Verdict Not Selected. After 2 days I was informed by HR that my profile and skills were very impressive, but they can't take my candidature further. I asked for feedback they told me that I need to work on my coding and problem skills.

Free preview — 6 questions shown. Unlock all Expedia questions →

About This Question

This is a reported interview question from a expedia interview for a swe role during the oa round reported in 2025.

It covers the following topics: Strings, Matrix, Graph, Stack Queue, Sorting, Graphs, Hash Table, Stack .

About Expedia Interview Reports

This question was reported by a candidate who interviewed at Expedia. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Expedia are the higher-signal extractions to take from this report.

For broader preparation context, the Expedia interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Expedia reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Expedia Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Expedia reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.