Between applying for the position, it took about three weeks before the company responded. I was given the outline of how the interviews for the phone screens as well as a brief idea of the expectations. Most of the questions that were posted on Glassdoor came up to some degree. First interview was a phone screen, mostly behavioral with very little diving into technical knowledge. After that, they followed up with a technical phone screen with the hiring manager, the question wasn’t too difficult (easy on Leetcode) but they seemed to be looking for other intangible skills that could benefit the team. The second phone technical was scheduled but unfortunately my interviewer had to be subbed in last minute due to an ongoing issue. Wasn’t a particular fan of that as that adds increased stressed on the interviewee of not knowing anything about your interviewer but luckily this worked in my favor. The second phone interviewer asked two easy/medium level questions and was cheerful but also understanding of the pressure which made it easier to think through my thoughts. The on-site was a little bit more challenging. The interview was broken into three technical interviews, a lunch behavioral and one remaining behavioral. Prior to going on-site, the recruiter couldn’t provide too much information, which is expected. The problems are closely related to the possible tasks that the team you may join do. A lot of it is can you program but more importantly can you identify where you struggle and find a solution. One was a system design, another was explanation of a project you worked on and how you contributed, where you voiced your opinion and technical design. The coding portion was related to building a feature using an API which closely resembles the core of the company’s product. All in all, I think the questions were fair. They weren’t hard per say but it focused more on skills needed to answer a question in a working scenario rather than purely leetcode problems. Despite doubting myself I was pleasantly surprised to receive an offer. I would say it it important to be confident in your system design and weigh the pros/cons of a solution before implementing.