GeeksforGeeks Experience · Jul 2025 · Bangalore

Amadeus Labs Bangalore Interview Experience(On-Campus)

Interview Experience

Amadeus Labs visited our campus in Aug 2019 for 2 profiles : ? Software Developer ? QA engineer The recruitment process was as follows: ? Online test. ? 2 Tech Rounds and ...

Full Details

Amadeus Labs visited our campus in Aug 2019 for 2 profiles : ? Software Developer ? QA engineer The recruitment process was as follows: ? Online test. ? 2 Tech Rounds and a HR Round. ONLINE APTITUDE TEST: The aptitude test was conducted on SHL Platform and had 2 sections: Numerical Ability(18 questions in 25 mins) and Verbal Reasoning (19 questions in 30 mins). There was no negative marking. 1) Numerical Ability For this section, we were allowed to use scientific calculators. It had questions on DI(data interpretation) which mainly consists of Bar graphs, Pie charts and tables. Makesure that you are fast with your calculations because time plays a crucial role as some questions were lengthy and required multiple computations. Overall the questions wereof medium difficulty level and a decent amount of practice can help you crack this section. 2) Verbal Reasoning For this section, a small paragraph of about 5-7 lines was given and each question had 3 options: 1) True 2) False 3) Cannot Say. Understand the questions properly and do alittle bit of research on how to tackle such questions before appearing for the test. Tips: Do not assume any information and strictly answer the questions based on what is given in the passage. Move on to the next question if you are not able to solve it. Around 35 people gave the test and 2 were shortlisted for further rounds. TECH

ROUND 1 This round was based purely on technical knowledge and went on for about 45 minutes. The interview began with a formal introduction. He then asked me to write a code to print prime numbers till 100. Next he asked me about all the searching and sorting algorithms I have studied in detail. He then asked me about all the OOP concepts and told me to explain method overloading and overriding by writing a code based on real life example. Later, I was asked about the data structures that I know and difference between each of them, which data structure should be used when. I was asked to name my favourite subjects in each semester I have studied and what did I like about it the most. Next he asked me 2 puzzles: Q1. https://www.geeksforgeeks.org/aptitude/puzzle-12-maximize-probability-of-white-ball/ Q2. https://www.geeksforgeeks.org/aptitude/puzzle-7-find-the-jar-with-contaminated-pills/ Lastly, I was also asked some HR questions in this interview like Why Amadeus, Why should we hire you and what you bring on to the table, etc. TECH

ROUND 2 This round was purely based on resume and what projects I have done. He asked me about the technologies used in the project, what was my role, why did we choose this as a project, which database was used, etc This round went for about 35 mins.

HR Round: The round started with my introduction. She asked my about my family background, what all certification courses I have done, my hobbies, why did I choose Engineering. She then asked me about Why Amadeus and why should we hire you. I was asked what recent article I read on technology and what are my views on it, since I told her that I am passionate about knowing the advancements in the technology. She asked me about my plans for further education and whether I was willing to relocate to Bangalore. This round went for about 30 mins. Results were announced on the same day and finally 2 students were selected.

Free preview — 6 questions shown. Unlock all Amadeus questions →

About This Question

This is a candidate experience report from a amadeus interview for a qa role during the oa round reported in 2025.

It covers the following topics: Graph, Math, Oop, Probability Stats, Sorting, Sql .

Difficulty rating: Medium

About Amadeus Interview Reports

This question was reported by a candidate who interviewed at Amadeus. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Amadeus are the higher-signal extractions to take from this report.

For broader preparation context, the Amadeus interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Amadeus reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Amadeus Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Amadeus reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.