Engineer I applicants have rated the interview process at Orbitz Worldwide with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 67.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Engineer I roles take an average of 11 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Orbitz Worldwide overall takes an average of 23 days.
Common stages of the interview process at Orbitz Worldwide as a Engineer I according to 2 Glassdoor interviews include:
One on one interview: 22%
Group panel interview: 22%
Presentation: 11%
Background check: 11%
Skills test: 11%
Phone interview: 11%
IQ intelligence test: 11%
Here are the most commonly searched roles for interview reports -
The process took 2 weeks. I interviewed at Orbitz Worldwide (Chicago, IL) in Jan 2008
Interview
After six phone interviews with a recruiter, HR, my potential manager and teammates, I came into the office for a personal interview with my potential manager, which was very short. The office was casual, laid back, and it appeared as if everyone was pretty busy, although there were a few people playing Foosball in the kitchen.
Interview questions [1]
Question 1
What was the highlight of your career so far of which you were most proud?
I applied through college or university. The process took 2 days. I interviewed at Orbitz Worldwide (Chicago, IL) in Nov 2010
Interview
Had a meeting with 2 representatives on campus. Very relaxed interview, they asked me to tell them the angle between the hands of a clock when it was 3:15 and to reverse a linked list.
The next round was an on-site interview comprising of an hour long skills test, some presentations and 2 interviews - one tech and one behavioral.
The hour long test was pretty straightforward with questions like simuate an RPN calculator, print first rep of a character in a string, count leaves in a binary tree, validate a BST.
The behavioral interview seemed to be the most intense with a group of people drilling you on your past projects.
The tech interview was again pretty straight forward with some data structures questions, some scheduling algorithm questions and finally how to detect a loop in a linked list.