Three candidates describe an Orbitz Worldwide software engineer interview with a behavioral discussion, data structures questions such as LRU cache and binary trees, and, for two of them, a take-home coding assignment.
$105K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
1-4 weeks
Process Length
Candidates describe an Orbitz Worldwide software engineer interview that mixes a behavioral conversation with practical data structures questions. Two of the three reports involve an on-campus round, and both of those candidates were later given a coding assignment: one offline, the other a 48-hour take-home.
The most repeated technical theme is LRU cache design, which appears in two of the three accounts. One candidate also saw string manipulation, and another was asked to find the nth element from the tail of a linked list and to validate a password against constraints. The third candidate reports isomorphic strings, a password check, rebuilding a binary tree from preorder and inorder traversals, and counting nodes and height. Hash maps came up several times. Candidates say interviewers cared about which data structure you choose and the time complexity of each option, so practice explaining trade-offs out loud.
Behavioral questions focus on teamwork and pressure. Reports mention your most challenging project, leading versus being a team member, handling stress, achieving a planned goal and resolving conflict with teammates. Have specific stories ready. One candidate also got a short brainteaser about the Earth's rotation.
Outcomes differ. Two candidates did not receive an offer. One of them stopped advancing at the offline assignment and wished for more clarity afterward. The third received an offer. Because the take-home removes interviewer hints, practice solving problems alone and writing clean, tested code.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Orbitz Worldwide process.
I interviewed at Orbitz in the summer of 2024, and the whole process took about four weeks from start to finish. The first round was an on-campus interview lasting around 45 minutes, split evenly between behavioral and technical questions. For the behavioral part, they asked about the most challenging project I'd worked on, how I'd lead a team, and how I approach collaborating with others. The technical side included string manipulation problems and implementing an LRU cache, which tested my understanding of data structures and design patterns.
I passed the first round and moved on to a coding assignment, which I had to complete offline. That's where things didn't go as planned — I didn't move forward after that stage. Looking back, the assignment was probably testing my ability to think through a problem independently without real-time feedback, which is quite different from the interactive interview setting. The people throughout the process were genuinely nice and helpful, offering hints when I got stuck, and they seemed to care about candidates' growth. They created an environment where you felt comfortable expressing yourself and showing your passion for the work, which I appreciated. That said, one frustrating part of the experience was the lack of communication at the end — I would have appreciated more clarity on why I didn't advance past the coding assignment.
Prep tip from this candidate
Focus your practice on LRU cache implementation and string manipulation problems before the technical round. Be prepared for an offline coding assignment that tests independent problem-solving — you won't have the safety net of hints from an interviewer, so work through complex problems on your own time beforehand.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Orbitz Worldwide
How would you answer when an Interviewer asks why you applied to their company?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Random SQL Sample | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Comments Histogram | |
| Upsell Transactions | |
| Google Maps Improvement | |
| Scrambled Tickets | |
| Flight Records | |
| Find the First Non-Repeating Character in a String | |
| Raining in Seattle | |
| Maximum Profit | |
| Completed Shipments | |
| Permutation Palindrome | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Recurring Character | |
| Rectangle Overlap | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an on-campus interview, reached through a college job fair in one case. One describes about 45 minutes split between behavioral and technical questions. Another describes a short behavioral part followed by a technical part of nearly an hour. Pseudocode on paper was used for some problems.
Candidates report questions about the most challenging project, leading versus being a team member, working with colleagues and supervisors, handling stress, achieving a planned goal and resolving conflicts. Interviewers appear to want concrete examples, so prepare specific stories rather than general statements.
Reported problems include an LRU cache, string manipulation, isomorphic strings, password validation, nth element from the tail of a linked list, and building a binary tree from traversals. Candidates say interviewers asked about data structure choice and time complexity, and may offer hints if you get stuck.
Two candidates report a coding assignment after the first round, described as offline in one account and as a 48-hour take-home in the other. Neither advanced past this point. It typically means working without live hints, so practice solving problems independently and verifying your solution before submitting.
One candidate says passing the take-home leads to an on-site with one technical and one behavioral interview, though this is second-hand. Outcomes in the reports vary: two candidates received no offer and one received an offer but declined it. One candidate noted little communication at the end of the process.
