Software Developer applicants have rated the interview process at Skyscanner with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 33.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 30 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Skyscanner overall takes an average of 19 days.
Common stages of the interview process at Skyscanner as a Software Developer according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 2 weeks. I interviewed at Skyscanner (Edinburgh, Scotland) in Jun 2016
Interview
A phone interview followed by a 70 minutes coding session on Hackerrank. The phone review went really smooth without many technical questions. I got two questions to for coding test and I ran out of time before finishing the second one. Usually the number of inputs are given in the exercise questions of Hackerrank but in the exam quesion, the number of inputs was not given (or I missed something as the clock was ticking). I spent a lot of time to figure out how to count the number of inputs on Hackerrank.
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.