Software Engineer applicants have rated the interview process at Skyscanner with 3 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 42.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 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 72 days.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Skyscanner (Singapore)
Interview
FIrst interview was a 30-40 minute phone interview to check whether it's worth their time to go for face-to-face interview with you. I was asked about my current job, a few technical questions regarding the tools I use, things that I love to do, programming languages that I know and whether I have open source projects, etc. I think they were also testing my communication skills during the phone interview.
Second interview involved difficult technical questions about software development, programming, scaling, software engineering processes and algorithms. There were difficult situational questions as well. I also took a short test which was difficult but I believe I managed to answer them correctly.
Interview questions [1]
Question 1
Write a pseudo-code with the most efficient algorithm possible for a particular puzzle.
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.