J'ai postulé via une agence de recrutement. Le processus a pris 2 semaines. J'ai passé un entretien chez Amadeus (Bengaluru) en févr. 2018
Entretien
First round was SHL test consist of logical and English questions. After that they called on their premises for technical rounds. I have given two rounds on that day before lunch, mainly focused on easy data structure and algorithms questions and little bit from previous projects . After that they said that as hiring manager is busy, I have to come one more day for hiring manager and Director round. Again one day they called me for hiring manager round. As the hiring manager was technical , the round went fine with discussion around designing solutions like e-commerce website and parking lot design.
At this point he asked me about my current ctc, expected ctc and my offers. After this he said I am asking a high amount and how can I justify this? I have asked for very reasonable ctc compare to status of Amadeus, I was really surprised with that response. Then he said HR will get back to me and voila I am rejected on basis of technical skills. I really wanted to work in Amadeus and this behavior really crushed my confidence. I really hope this doesn't happen to anyone.
Se hacen 3 entrevistas, una con hr, luego va la entrevista de code challenge y finalmente una para conocerte mas. El code challenge con ejercicios de leet code y es presencial
Questions d'entretien [1]
Question 1
Que arquitecturas que he implementado y por que las he usado
J'ai passé un entretien chez Amadeus (Londres, Angleterre)
Entretien
The interview process consisted of one behaviour and then one technical. Leetcode style questions. Object oriented programming questions. The more questions you answer the harder the follow up questions get.
Iterview with HR:
They check if you are a good fit for company values
Direct management:
Again check if fits with team culture and technical and academic background and experience
Technical interview:
some that i've seen includes system design, theoretical knowledge on software dev like concepts of o.o.p.
for programing usually check if a given code works why it works and why its failing also check for errors in syntax and semantics