I had an initial call with a recruiter. After that call, I was passed on to a new recruiter who took two weeks to email me. She only replied to me once I reached out to her directly.
She scheduled a call with me to inform me that the company had over-hired in other areas, which explained the delay. She told me they were still hiring for my position, so a coding interview with one of their developers was scheduled.
The coding interview went pretty well. The question was fairly practical, not obtusely difficult (like something useless such as recursion), but not 100% straightforward either.
I received feedback from that interview fairly quickly, informing me that I had made it to the final stage. I had a call with the recruiter to try and schedule the final interview. I couldn't do the day she suggested, but she said she would get back to me about scheduling it for another time.
I never heard back from her, and she ignored all my attempts to contact her. I was completely ghosted.
Overall, it was very frustrating and disappointing to get this far through an interview process and then receive no explanation as to why it didn't work out.
Typical recruiter questions and typical coding interview problems on HackerRank.
The following metrics were computed from 7 interview experiences for the Expedia Group Software Engineer role in London, United Kingdom.
Expedia Group's interview process for their Software Engineer roles in London, the United Kingdom is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Expedia Group's Software Engineer interview process in London, United Kingdom.