I was contacted by a recruiter and, after a phone call, filled out some information. I was then set up with a phone screening.

About five days after my phone screening, my recruiter contacted me again and told me I would be moving on to the onsite interview.

I was then placed in contact with another recruiter at the location where I would be interviewing. Over the course of about a week and a half, we set up my trip out there.

Once on campus, I had four interviews, lasting about 45 minutes each, and a lunch interview.

They asked the average tricky coding questions. I would talk through an algorithm with the interviewer and then put the algorithm into code.

About two weeks after the onsite interview, I reached out to my recruiter for feedback. We scheduled a time to call within the next couple of days, and I was informed I wouldn't be moving on or getting an offer.

It was a pretty good interview process if you're familiar with the whole coding interview game. I was thankful that I was able to get an answer within two weeks, as Google can sometimes go a little long without updating you.

Most problems happened to be about some kind of string parsing/manipulation (palindrome problems, word detection, etc.).

However, the one I had the hardest time with was an array-based find all subsets problem.