Real, anonymous reports from people who interviewed for Software Engineer at Amadeus, newest first and distilled into what to expect across the loop.
After a recruiter chat with HR, the process moved into a few back-to-back rounds. I sat through a two-person technical discussion that included a company controls manager alongside an engineering manager, and then I had another 2v1 session with an engineering manager and that first recruiter again. The overall tone felt pretty steady—definitely not chaotic—but I could feel the focus tightening as the rounds went on.
My process started with a screening step that felt straightforward and recruiter-led, followed by a technical portion that leaned on coding-style evaluation. I ended up doing a coding assessment first, and then there was either an additional quantitative aptitude component or a follow-up technical interview where I worked through coding questions. The on-campus and online variations all followed a similar rhythm: first they test the basics in a structured way, then they talk to you about how you think.
The interview process typically starts with a recruiter screening, followed by multiple technical rounds that may include coding assessments and HR discussions. Candidates reported a clear structure, often involving a mix of technical and behavioral evaluations across several stages.
Candidates faced a variety of technical questions, primarily focused on data structures and algorithms (DSA), with some also including object-oriented programming and system design elements. The coding challenges ranged from medium to difficult, often resembling LeetCode-style problems.
Behavioral interviews were generally straightforward, focusing on motivation, past experiences, and situational responses. Candidates noted that these discussions were less about technical traps and more about fit and communication skills.
The overall difficulty of the technical rounds was reported as moderate to high, with some candidates feeling increased pressure as interviews progressed. The challenge often stemmed not just from technical knowledge but also from maintaining composure under escalating questioning.
Candidates emphasized the importance of clear communication during technical discussions, particularly when explaining their thought processes and previous projects. Miscommunication or unclear expectations could negatively impact the interview experience.
While some candidates appreciated timely feedback throughout the process, others experienced delays or lack of communication after interviews, which affected their overall impression of the hiring experience. Consistent updates were noted as a positive aspect.