HR informed me two days in advance that a series of four telephonic interviews were scheduled, spanning across two days.
HR was friendly throughout the process and kept me updated.
After two levels of interview, they informed me that they wouldn't be able to proceed with my candidature further.
They shared the feedback of the interview on request, which was helpful.
Contrary to my assumptions, I found the interview pattern simple. Each interview lasted for 1 hour and consisted of 3 questions precisely:
a. A quick question about OOPS. b. A question related to functional programming: preparing an exhaustive test case list for a typical web service architecture. c. A coding question: a typical challenge involving arrays and matrices, where they expect you to arrive with a design and code within the stipulated time.
Trust me, they expect finely tuned code on the first attempt. No excuses.
Interviewers might give some focus points if they think you are missing something or lacking. Try to seek out that point and explain your approach to that area. You cannot skip that point.
Preparation around coding challenges involving arrays, strings, matrices, and linked lists would be helpful.
The following metrics were computed from 1 interview experience for the Expedia Group Software Engineer In Test - II role in India.
Expedia Group's interview process for their Software Engineer In Test - II roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Expedia Group's Software Engineer In Test - II interview process in India.