Expedia Internship Interview Experience | On-Campus 2021
Question Details
Expedia visited our campus for a recruitment drive, providing an exciting opportunity for students to showcase their skills and secure positions in their esteemed organiza...
Full Details
Expedia visited our campus for a recruitment drive, providing an exciting opportunity for students to showcase their skills and secure positions in their esteemed organization. Education: Btech 3rd year ECE student of Tier-2 Online Test via Hackerrank: The online test was proctored and we were not allowed to switch between the tabs or copy past our code on the editor. 120 mins test with three coding questions. 2 easy, one medium. The two easy ones are one from array n and the other from string. The medium one is a knight chess problem. The starting and ending coordinates of the knight were given, and we need to find the minimum number of moves to reach the ending coordinate from the starting coordinate. This was a dp problem. I solved all three problems quickly without any difficulty. Out of 200+ students, 46 students we shortlisted for interviews.
Technical Round 1 via Zoom Meeting: Time duration was 45 mins, and the interview asked only one coding question. Question Asked: You are given a list of numbers in the form of a string array. Find the largest possible number that can be created by appending these numbers one after another. First I thought of an example : ["2","41"]. I asked myself which number would come first, the "41" one. Why? As "41" is lexicographically larger than "2,". So the final answer is "412". So my final approach lexicographically sorted the array in decreasing order and appended all the strings in the order. My interviewer then asked me to code it. The interviewer also asked me what improvements could be made to my code. Suppose you are writing code in a project, then what coding practices should you follow? I said I would document my code, and then he told me what more? I could not think of anything, so he said you should use proper naming conventions and not duplicate your code as well. The interviewer told me that you are going to the
next round.
Technical Round 2 via Zoom Meeting: The time duration was 45 mins, and the interview asked two coding questions. Question 1: Evaluate a given postfix expression, a famous question on the stack. As soon as I got the question, I told my approach, and then the interviewer asked me to code it and its time and space complexity. He was satisfied by my approach. Question 2: Word Search . You are given a 2-D grid of characters and a string, and you need to find whether, upon traversing the grid, you can find the word or not?.
Note: from a cell, you can only go to adjacent cells with common edges. So I coded this problem using backtracking. He asked me about the time and space complexity. I said O(4^nm) time and O(nm) space. But then he corrected, and the final time complexity was O(4^|word|). He was also satisfied with my approach.
HR round via Zoom Meeting: After the 2nd technical round, I got a phone call from the Expedia recruitment team, and they scheduled my HR round meeting with the product manager. She asked about myself and my hobbies. Then she asked about my location of living. Then she asked me where do you see yourself after five years. I said that in 1st three years, I would gain domain expertise, and in the next two years, I will explore other domains of the company. Then she gave me a scenario where you and your friends are working on a project, and during the final production, you see there is an issue with your friend's code; then what would you do?. Then we talked about the company a bit, and it ended after 45 mins as well. Out of 46 students, 20 students got selected for the internship, and guess what? One of them was me. Some bonus points: Don't stress yourself and be calm when answering. Always follow good coding standards like proper naming conventions. Tell the time and space complexity of your approach even if they don't ask it. If you get stuck, the interviewer will help you.
About This Question
This is a reported interview question from a expedia interview for a pm role (intern level) during the oa round reported in 2025.
It covers the following topics: Strings, Matrix, Dynamic Programming, Stack Queue, Recursion, Backtracking, Arrays, Stack .
Difficulty rating: Easy
More Expedia Interview Questions
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.