Overall, the process was very smooth. A recruiter emailed me and asked if I was still looking, to which I replied yes. She then set up a time to talk about what I was looking for.

After that, she asked me about 20 CS trivia questions, which I found to be a weird part of the process. Firstly, they were basic CS questions, and not knowing them wouldn't tell them anything about a candidate's ability to perform. Secondly, the recruiter didn't have a technical background, so if any of the questions had alternate answers not on her cheat sheet, she wouldn't know.

Following this, she arranged a Skype interview. The interviewer was interested in some aspects of my resume, which was great, as most interviewers jump directly into coding. They then asked me to code a simple problem just to check my coding ability. I passed this and had another Skype interview where I was asked to code a more complex, but still not difficult, question.

I was then invited on-site for five rounds of whiteboard coding. All the questions were straightforward. They are looking at your thought process, not how fast you come up with a solution or if your solution is perfect. The interviewers were very nice and would help you if you got stuck, so thinking out loud is recommended. None of the questions required advanced knowledge of complex data structures like Fibonacci heaps or n-ary trees; brushing up on the basics is sufficient. Also, the interviews are language-agnostic.

After the on-site interviews, if they decide to move you forward, they will ask for three references and then present an offer, which was a great conclusion to the process.

I signed a Non-Disclosure Agreement (NDA), so I will not reveal specific questions. However, I can share that preparation involved reading about how to use lists, sets, and maps. It was also beneficial to study sorting techniques and determine the best data structure for a given use case. Most questions can be answered with knowledge of these topics. The key is to keep it simple.