I applied through college or university. The process took 3 weeks. I interviewed at Google in Nov 2016
Interview
I applied in a university career fair, and get a on campus interview after 2 weeks. It was two back to back 25 minute interview with two recruiters, and the questions they asked were pretty normal questions you would find in Leetcode or Crack the coding interview . The recruiters are very nice and the HR is responsive. (you have to fill tons of forms ,sign NDA and one online assessment before the interview,)
I applied through a recruiter. The process took 3 months. I interviewed at Google (Mountain View, CA) in May 2016
Interview
Overall process took 14 weeks
The recruiters were very friendly and helpful.
Week 1 Recruiter emails to set up phone screen
Week 2 Recruiter phone screen: informal phone call with recruiter to discuss your current projects and skills
Week 4 Coding sample: they give you link to 2 coding problems you have to solve in 60 mins
Week 9 One phone interview with google docs: this is where most of the filtering of candidates happen. I delayed this for 4 weeks to review. Interviewer was helpful and was not intimidating. Make sure you walk through your thinking and not go straight to coding. 2 problems, was not able to finish the 2nd one but I told him my approach. Make sure to engage the interviewer throughout the 45 minutes. They will give you a broad problem, so ask questions!
Week 12 Onsite interviews: the most fun interview experience I've ever had! They're campus is awesome. They book you to this very nice hotel with shuttle to the campus. They pay for hotel and flight, reimbursements for food and ground travel expenses.
2 interviews in the morning, lunch with another engineer (not an interview), 2 interviews in the afternoon. First 2 interviewers were really friendly. 3rd interviewer was kind of intimidating. He was on his laptop don't know if he's taking notes or doing his own thing. I was still able to engage him a little bit and was still able to come up with a solution. 4th interview was where I screwed up. The interviewer was from an Asian background and I could not understand most of the words she was saying. I wasn't prepared for the question. It was with a lot of analysis and math.
All interviewers take pictures of your code for every progress and fixing of bugs you make.
Approach to all interviews: ask questions, talk through your approach, start coding at the same time talking to what you're writing, do testing
Week 14 Recruiter called me they cannot give me an offer. I was kind of expecting this because I knew I have to nail all 4 interviews. They cannot disclose any information regarding the decision
I may not have received an offer, but going on-site was such an amazing and memorable experience!
Interview questions [1]
Question 1
data structures, algorithms, time complexity
trees, hashmaps, lists, strings, graphs, coding design, OOP principles, searchs, sorting, traversals
they give you a study guide. make sure to review all of those.
Cracking the Code Interview and Hackerrank definitely helped me prepare
I applied through college or university. I interviewed at Google (New York, NY) in Mar 2016
Interview
Skipped the phone screen because I had limited time. Went straight to on site at NYC, thought i did well on all of the 4 technical (1hr each) interviews. Got a call from the recruiter a couple of weeks later saying I had done really well on the interviews and received positive feedback, but the hiring team did not think I had enough previous experience for the position, was referred to another (more entry level position, did not pursue).