I had a phone screen which was a live coding exercise on something aligned with my specialty. I was surprised by the exercise because it was somehow theoretical, but there was no trick question and it wasn't overly difficult. the interviewer would have been ok with me looking up documentation but my internet connection being really bad, I just went ahead and explained my process. I had very rapid feedback on that interview. In fact, the next time I checked my phone after doing the screen I was already invited to an onsite. On site i had 5 interviews. Overall, the interviews were much more about high level process and thinking than coding proper. Other reviews I read, and the recruiters email, prepared me to code on my computer (and again having access to documentation if needs be). In total, I had 2 functional brainstorming sessions ie how would you solve this problem - with problems squarely in my specialty. I had other exercises where I was asked the same but with a technical problem that was pretty different from what I usually do, and for which I had to write pseudocode (on white board). In my first interview, I had some trivial coding questions. I also had a more discussion type interview about values, past experience, etc. I must say it's not easy to get a sense of what are uber values/culture from the website. So I just tried to be true to myself and show what I do care about. My last interview had more classic interview problems on white board. I did 3 exercises which were mostly on the fine points of javascript syntax and structure. Those were not easy especially towards the end of the day. All in all I was surprised that questions stayed mostly high level, that made me more comfortable as I feel strongest there.