Software Engineer applicants have rated the interview process at Skyscanner with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 56.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 28 days to get hired, when considering 28 user submitted interviews for this role. To compare, the hiring process at Skyscanner overall takes an average of 35 days.
Common stages of the interview process at Skyscanner as a Software Engineer according to 28 Glassdoor interviews include:
Phone interview: 30%
One on one interview: 18%
Skills test: 17%
Group panel interview: 12%
Presentation: 12%
Personality test: 7%
IQ intelligence test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Skyscanner
Interview
Applied online, had to take a 40-minute IQ test and a short personality test. Two weeks later I have been called for a phone interview, with general and behavioural questions(-Why Skyscanner? -What are your passions? -How do you ensure that you keep learning?). At the end of the interview I was told the results of my personality test and the IQ test(which had gone very well apparently).
Interview questions [1]
Question 1
Tell me about a time you had to take an impartial decision
For software engineer role it was very detailed interview process at multiple stages, including coding test, and multiple system design interview. I must say it was a great experience and learning.
Wonderful experience, I can tell them what I truly want. Hope to join the team and do what I want to do. The interviewer is so kind, allows me to think longer when I don’t know how to answer questions.
I applied online. I interviewed at Skyscanner in Apr 2026
Interview
I interviewed with Skyscanner.
The HR process was professional and well-organized. Communication was clear, and I appreciated that they offered to provide feedback afterward.
The technical interview, however, was disappointing.
The interviewer was not very communicative and didn’t provide much clarification when I asked questions about the task, which made the process feel less collaborative than expected.
I implemented a working solution during the interview, focusing on correctness and efficiency. While it may have had minor syntax issues or missed some edge cases due to time pressure, it addressed the problem.
At the end, I was surprised when the interviewer suggested that I might have copied the solution.
This felt unexpected and unfair, especially in a live coding setting where the thought process is visible.
Interview questions [1]
Question 1
There were two coding problems: the first was easy, and the second was a graph problem.