I applied online. The process took 3 weeks. I interviewed at Skyscanner (Edinburgh, Scotland) in Dec 2016
Interview
Stage 1: Hackerrank
Stage 2: Skype
Stage 3: Edinburgh headquarters interviews
30 minute Skype interview was composed of competency questions about myself.
During the headquarters application process we were firstly asked to (as a group of 6) create a project of Skyscanner rating system, and present our solution including UI, technical and more broad evaluations.
Later 50 minute technical interview was concentrating on a technical implementation and structure of a car hiring data model. It did not require any specific deep technical knowledge, but rather intuition of a data model structure.
Cultural interview was more standard job interview, but very pleasant.
In all of the situations interviewers were extremely helpful, polite and created a professional yet friendly atmosphere that made me learn new things and really enjoy the process.
Interview questions [1]
Question 1
Desing a Skyscanner rating system. Why do I want to work for Skyscanner?
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.