A recruiter initially reached out to me through LinkedIn.

After a few phone call interviews, I moved on to a few remote skills exercises. I didn't interview for a specific position; instead, I was told that the position the company thought I was best suited for was determined through the interview process (whether I was senior or staff level, or whatever).

I had two screen-sharing interviews, which were coding exercises where two developers from LinkedIn would give me specific challenges or examples and ask me to solve them or work through them. Each was about 45 minutes, with 30 minutes of coding and 15 minutes for questions, introductions, or other discussions. The first covered JavaScript, while the second covered HTML and CSS. Even though I was coding in a web interface, the code didn't compile or actually show UI. I think this is so you don't get distracted with the minutiae of making something actually work and instead focus on strategy and the overall steps to achieving your goal.

After these first skill assessment interviews, I was flown out to Mountain View to interview at their campus. The on-campus interview was pretty much a full-day process. I started off with a brief tour of the office and some discussion about the company's background with one of the people I had exchanged emails with during the early phases of the process. Then I was taken to a meeting room where the rest of my interviews would take place.

There were six or seven groups of interviews. The first two were general information about the company and the team. Then there were four technical interviews, each with a pair of developers (one senior, one junior). Each addressed different aspects of development: CSS, HTML, JS, etc. There was also a lunch interview, which is when you just grab lunch with another developer. Each of these interviews followed a similar format to the phone interviews—about 45 minutes each, with around 30 minutes of coding and 15 minutes of general questions. Also, the technical challenges were all done on a whiteboard, without a computer.

During my phone JS interview, I encountered many general CS questions.

These questions were a bit frustrating because they're things you know you can just Google and find the one-line answer you need without any actual effort.

Examples include writing a function to determine if a string is a palindrome or writing a function for the Fibonacci sequence. These are common stereotypical interview questions that don't have much real-world application.