This was an almost entire day technical interview. This was not in Seattle or Vancouver, so a few interviews were remote, but still I had to write solutions on a white board. This was not very different from what is described in the Cracking the Code Interview book. Lots of focus on Big O notation and scalability. I had a couple interviews in the morning, then one of the guys took me out for lunch and three more in the afternoon. Data structure and Big O notation are the big focus, while you design solutions on paper, white board, or plain text editor. Each interviewer has a different preference. Lots of behavioural questions, but also the expected things. Basically they ask you about the most challenging situations and how you handled them, like when your vote on a solution was overruled, or when you had to throw away a lot of code and start from scratch again.