Orbitz Worldwide Software Engineer Interview Questions
& Process

I hit up the campus career fair and dropped off my resume. A couple of weeks later, maybe 2 or 3, they pinged me for an on-campus interview that lasted about 45 minutes. It was a mix of 3 behavioral and 4 technical questions covering a simple math problem, BFS on a graph, BSTs, and a recursive programming task. Then, two days later, they sent over a coding test, which I got from Friday to Sunday night to complete. It seemed like undergrad homework difficulty, expecting perfect work given the 2.5 days. I just finished it and I'm waiting to hear if I'll get invited for the onsite, which they mentioned would be three weeks after that. The interviewers were really nice and friendly.

HR called me first to talk about the job, benefits, and my interests, also explaining what's next. Then, a tech phone screen where they asked basic Java and general software questions, checking my CS knowledge and background. No tough brain teasers, just a sorting question. After that, a coding assignment over the weekend – got an email with a problem and had Friday to Sunday to solve it. It took about 8 hours, including JUnit tests, and wasn't too hard if you know Java and JSON. Finally, the onsite was well-organized with a clear agenda. It started with a tech round where I had to explain my current project and whiteboard some code, followed by questions about the code I wrote.

I first met the Orbitz team at the campus career fair and then applied for the position on the campus career website. About 10 days later, I was selected for an on-campus interview that lasted an hour. It was split into two parts: 30 minutes of behavioural questions and 30 minutes of technical questions. They asked typical behavioural questions. For the technical part, it was all about Data Structures and Java Programming. A week after that, HR called me and sent a programming assignment which I had to submit within 2 days. After that, I got a call for an on-site interview. This interview was 2 hours long, with 1 hour dedicated to behavioural questions and 1 hour to technical questions. I was told to be ready to write code and algorithms. Apparently, they asked the same 4-5 questions to all candidates. There were about 80 candidates from various colleges competing for around 20 positions. The rest of the day involved speeches from the CEO and CTO, followed by lunch. It was an all-day event.