First stage was a phone screen with one of their engineers. The problem wasn't really a Leetcode type problem and more about getting working code. After I passed that I made it to the onsite stage. The onsite consisted of a behavioural interview, system design interview and 2 coding interviews. The 2 coding interviews were again not really Leetcode type problems and they required you to bring your own laptop to do the work. They woudn't let you bring your work laptop so I had to bring my personal laptop. Unfortunately I didn't practice coding on it beforehand so I was not used to various shortcuts which slowed me down. The first coding problem to create a hashmap wasn't too difficult but the one to fix a bug in an open source library was a bit trickier. I assumed I could just scan through the code to find the failing line then fix it. But due to the code style being so different to what I was used to, it was quite hard to follow what was happening. In hindsight I would have started by putting print lines to try and understand the code first before trying to identify the code changes to make.

15 minute call with their recruiter, followed by initial screening round, which was a coding exercise (not leet code, more like string/array manipulation). After passing that, I had to do 6 rounds of: - System design: whiteboard problem, the guy was pleasant and helpful, but I bottled it. - Backend integration: Tests your ability to develop a REST api, easy enough. - Culture: General conversation over career and goals. - Bug squash: They give you a failing test, and you have to fix it. I managed to fix all suites but I didn't perform very well here bc my methodology wasn't strong enough I believe, and the guy wasn't very pleasant (bit pushy but still professional) The interview process was very long and exhausting, but it truly tests your ability as a software engineer without resorting to leet code.