I had an initial phone screen with a recruiter, then a take home test. The take home test was a timed 45 minute coding challenge on codility, there were two questions. The first was easy enough, the second one took me a bit longer and I didn't quite finish it but still got through. The next stage was a one hour chat with an engineering manager. It was mostly general questions and questions about my technical experience but not technical knowledge (Describe your proudest bug fix, how did you de-bug it?). The next stage was 3 face to face interviews each with one person, all technical. This would normally be on-site but for me it was over zoom because of covid. Two interviews involved sharing your screen and solving a coding problem. One was easy for me and another was a bit trickier. All the questions were general algorithmic coding challenges and don't require a specific knowledge set other than just being able to solve problems and write an algorithm without googling it. I appreciate this approach as it's language agnostic. I saw another review which recommended a book called "Cracking the coding interview". You don't have to read all of it but the first few chapters will give you a sense of what they ask. The other interview didn't involve sharing my screen but there was a lot of technical questions surrounding TCP/IP protocols, difference between http and HTTPS etc. I got turned down after this last stage and my recruiter offered to phone me to give me feedback next week. The recruiter was great and the process moved very fast. I really got the sense that they want applicants to have a good experience which I did. My only recommendation would be maybe shortening the whole process or number of interviews. It is quite frustrating to go through a phone interview, coding challenge and 4 hour long interviews only to be turned down at the very last step.