Software Engineer applicants have rated the interview process at Skyscanner with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 44% positive. To compare, the company-average is 39.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 17 user submitted interviews for this role. To compare, the hiring process at Skyscanner overall takes an average of 37 days.
Common stages of the interview process at Skyscanner as a Software Engineer according to 17 Glassdoor interviews include:
Phone interview: 27%
Skills test: 24%
One on one interview: 14%
Presentation: 14%
Background check: 8%
Group panel interview: 8%
Personality test: 3%
IQ intelligence test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 5 days. I interviewed at Skyscanner (Barcelona) in May 2015
Interview
I received a phone call from an internal recruiter. We talk about the company, what they were looking for and my skills and past experiences. Few days later I did a coding challenge on hackerrank. It was basically 3 questions and I had to create algorithms to pass some test cases.
Interview questions [1]
Question 1
Write function to calculate sum of first N powers of 2 starting from 1. You shouldn't use any built-in function for calculating power. Implement the most efficient solution.
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.