The interview process consisted of three steps conducted via Skype.

The first interview was with an HR representative and was standard and rather uninspired.

The second was a Q&A session on various programming subjects, including networking, hardware, databases, big data processing techniques, and binary logic and arithmetic. These topics ranged from what they considered easy to more difficult.

Once you missed one or two questions in a subject, they would change topics. I recommend being honest in this situation. I guessed several answers based on hearsay and common sense rather than actual familiarity with the terms asked about, and I still did well. However, I do recommend supplementing your answers with phrases like, "I'm not familiar with that specific term, but it sounds like it must be..." I believe this company values common sense and capacity over sheer rote knowledge.

The third interview was a live coding test in the language of my choice. It covered fundamental Computer Science concepts such as trees and graphs, as well as mastery of the chosen language.

I ultimately failed this test due to nervousness. I was tested on graphs, a topic I hadn't worked with in a long time, while my preparation had focused specifically on trees. Consequently, I was unable to produce a Breadth-First Search (BFS) algorithm. In retrospect, I really should have googled for pseudocode instead of trying to recall it from memory.

Following this, there would have been a fourth interview on-site. This interview apparently involves designing solutions to real-world problems faced by the team you are interviewing for. They would have paid for travel and a one-night stay in Stockholm.

What messages are exchanged in a TCP handshake?