I had an initial phone screen with a recruiter to discuss the role and my experience, this was only about 15 minutes. There were 3 surprise technical questions at the end but were simple to answer (name some data structures, what time complexity is a particular algorithm) I then had a technical screening, this was done over bluejeans and coderpad, you're given 1-2 problems and have to code the solution with the interviewer on the call. You can pick the language you want to code in and the problems they pick tend to be very general algorithms. The next stage was a "full loop". this was 4 interviews grouped into one round. One was technical/coding, one was cross functional collaboration, one was troubleshooting and the last one was general/career expectations. If you do get to this stage, the recruiter will probably give you tonnes of help and questions to practice for all four interviews. Normally this would be the end but they scheduled another technical coding interview for me. The hiring manager wanted to hire me but my technical test during the full loop could have been better so they scheduled another one for me to be sure of my coding before offering me a job. Some general tips: treat any advise your recruiter gives you as gospel! They're not trying to trick you, they are genuinely trying to set you up to succeed, if they give you the exact wording for questions that may come up then prepare an answer because in my experience, some of the questions were asked word for word. The book "Cracking the coding interview" gives a great insight to the type of technical questions you may be asked about. Understanding time complexity and Big O notation is very important Everyone I met was very friendly and my recruiter kept me updated the whole time. My process went on a bit longer then they had planned but my recruiter apologised and explained the delay to me. There's a lot of prep work to do to succeed but they will give you a lot of pointers on how to prepare.