eDreams ODIGEO logo

eDreams ODIGEO Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 23 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
65.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at eDreams ODIGEO.

Showing 3 of 23
eDreams ODIGEO logo
eDreams ODIGEO

Software Engineer

Engineering · a year ago

Mid Average Negative experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

It started with a basic chat with HR, followed by a meeting with a solutions architect, and then a 1.5-hour session with two senior engineers. The interviews were packed, leaving little room for discussion. They covered standard questions, SOLID principles, Microservices, Design Patterns, and a Battleship coding exercise. Some parts were cut due to time. A weird part was being told I wasn't a good fit for the role but could be if I moved to Spain. When I asked about other opportunities in my country, I had to wait a week, only to be told I wouldn't fit any roles, even ones they previously said I was qualified for. The whole experience with broken English from HR and slow email replies was quite something, especially for a company with high standards.

Confirmed questions5 questions
  • Can you explain SOLID principles?
  • What are your thoughts on Microservices?
  • Compare and contrast Hashmap, Hashtable, LinkedHashMap, and TreeMap.
eDreams ODIGEO logo
eDreams ODIGEO

Software Engineer

Engineering · a year ago

Senior Easy Positive experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

The interview process was fine and started with usual HR type questions but ended with few Java questions as well which was very odd to me to be asked in an HR interview. Even the interviewer told me we need to enhance this piece of our interview process later on! It only take me the first HR interview to fail which I am not sure what was the reason and I also sent a follow up email to the recruiter to ask what the reasons were and I did not get a reply back at all!

Confirmed questions3 questions
  • What is the biggest achievement on your career path so far and why does that considered as an achievement for you?
  • What is your biggest career achievement and why was it important?
  • Describe your most significant professional achievement and explain why it stands out.
eDreams ODIGEO logo
eDreams ODIGEO

Software Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical Coding Behavioral

The interview process was pretty simple. First, there was an HR screening, followed by a 30-minute meeting with the hiring manager to get acquainted. After that, a 2-hour technical round happened, covering coding basics like SOLID, Hashmap, abstract classes, heap/stack, multithreading, garbage collection, databases, and indexes.

Confirmed questions4 questions
  • Could you take a look at the Battleship game code and identify any issues within a specific class?
  • How would you make a class in the Battleship game code immutable?
  • Please fix three given test cases for the Battleship game code.

eDreams ODIGEO Software Engineer Interview Questions

Quoted word for word from eDreams ODIGEO interview reports.

What is the Big O notation for inserts in standard Java collections?

Read reports

How would you make a class in the Battleship game code immutable?

Read reports

How would you optimize a method that finds duplicates?

Read report

Can you explain what a transitive Maven dependency is?

Read report

Could you take a look at the Battleship game code and identify any issues within a specific class?

Read report

Formats, difficulty and experience

Across all 23 eDreams ODIGEO interview reports.

Interview formats

Technical 33.8%
Behavioral 26.2%
Coding 26.2%
System Design 10.8%
Other 1.5%

Interview difficulty

Easy 30.4%
Average 60.9%
Difficult 8.7%

Candidate experience

Negative 21.7%
Positive 65.2%
Neutral 13%