
eDreams ODIGEO Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 178 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 178 reportsCandidate interview experiences
First-hand accounts from people who interviewed at eDreams ODIGEO.
Frontend Engineer
Got through to the first phase, which included typical HR queries alongside technical questions about JavaScript. These technical questions were posed by a non-technical recruiter, meaning you couldn't elaborate or seek clarification. I was rejected because when asked about a specific skill set, I attempted to discuss it rather than simply saying 'yes'. They logged it as a 'no', and the engineering team rejected me. I reached out to the recruiter to clarify that I do possess those skills, but was ignored. The call itself was okay, and the recruiter seemed to try to make me comfortable, but this process isn't right.
- Tell me about yourself / general HR questions.
- Standard JavaScript questions.
- Standard React questions.
Document Management Specialist
The process began with an email from HR for an initial call on 02/09. I had to reschedule due to illness, and HR was understanding. The first call went okay, despite me not being at my best, and I mentioned this. I was told to 'be sharper' for the next step. The second interview on 10/09 with the hiring manager was positive, with good alignment on expectations and experience. I was then invited to prepare and present a business case, which involved significant research and analysis. This session went reasonably well. I received a rejection email on 18/09 stating they were moving forward with candidates with more data-focused processes, which was frustrating given my discussed data background. I requested personalized feedback but received no response. Weeks later, on 14/10, HR contacted me about a new opening for the same role with a reduced salary, claiming it was restructured from Executive to Specialist, though the original description was always Specialist. I agreed to continue. A new call was scheduled for 15/10 with a second manager who had seen my presentation. I confirmed my availability and remote work capability. After this call, there was no further news despite my two follow-up emails and a LinkedIn message.
- Tell me about challenging situations.
- What are your aspirations?
- Can you describe challenging situations and your aspirations?
IOS Engineer
The whole thing felt a bit all over the place and not very clear, which was a bummer because I got referred and heard good things. I ended up talking to three different HR people and got shuffled between jobs without much explanation. This meant more interviews than I expected, and they even tried to switch up how they were evaluating me mid-way. Things were on hold for two weeks before picking back up, which just dragged it out even more. After over two months, I got an offer that was less than I was hoping for, lower than what we talked about in the first chat, and even less than my friend who just started there is making.
- In the initial HR meeting, we went over my past jobs, the position, and what I'm looking for salary-wise, and I responded to some hypothetical scenarios.
- During the technical interview, they explained the job again, gave me details on the company, its operations, and how they work, and I answered hypothetical questions as well as specific technical questions about software and iOS development.
- In our third conversation, we discussed the technical project I completed, where I presented my approach and answered some basic questions about the included tests.
Frontend Software Engineer
The interview process had 4 steps, with the last one being optional for senior folks. First, an HR video call where they asked some theoretical Javascript questions that the tech team came up with (45min). Then, a Hiring Manager interview to discuss the role in more detail (30min). After that, a technical interview (1.30h) where I had to complete 3-5 exercises on CodeSandbox. These exercises involved fixing, completing, or adding features to pre-compiled vanilla Javascript and React code. Finally, there was an optional take-home project for senior positions.
- How would you correctly pass the "this" object inside a callback within a function, especially when "this" is invoked and reassigned?
- Refactor a basic React interface: initially, it should take string inputs, add them to an array, display them, and allow removal. Then, modify it to work with objects and their properties instead of just strings.
- Create a dictionary representation using an appropriate type and implement functions for inserting and removing key-value pairs, where the key is a word and the value is its description.
eDreams ODIGEO 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 →“Could you re-implement the JavaScript String.indexOf() function using only String.charAt() and no other built-in functions?”
Read reports →“Create a dictionary representation using an appropriate type and implement functions for inserting and removing key-value pairs, where the key is a word and the value is its description.”
Read reports →“What angle do the hands of a clock form at 3:15?”
Read reports →“How would you make a class in the Battleship game code immutable?”
Read report →“What is the difference between a transactional table and a dimensional table?”
Read report →“Can you create an algorithm to check a string input for a specific substring format?”
Read report →“Why is an MCP server better than a direct API query?”
Read report →“Could you implement unit tests for your indexOf() function? Using Mocha.js would be a bonus.”
Read report →Formats, difficulty and experience
Across all 178 eDreams ODIGEO interview reports.