Live data from Hacker News

My Google Interview Experience

news.ycombinator.com

1–10 of 88 posts

My Google Interview Experience

#1
I recently went through the full breadth of the Google Interviewing process for the Software Engineering role. I didn't make it through, but that is not what made me upset, instead it was the lack of proper feedback on Google's side.

While I understand that they have legal issues giving out feedback, but I don't see why they can't dish out simple numeric scores for each of the interviews. That will at least make the candidate aware of how much he needs to improve, or if he can even improve enough to apply again, or it's just not worth retrying. This is specially expected from Google since they ask you to prepare a ton of material for around a month which is real hard work.

Anyways on to the real stuff. I cleared the only phone interview, which was very basic, shared Google Doc coding for about an hour. I was then called for a set of 5 onsite interviews, which were 45 minutes each. While I won't give out the exact questions because I want to abide by the confidentiality agreement, I will just try to summarize.

Two were design and implementation, two were algorithms, and one was algorithms and implementation, all of them required writing on the whiteboard. I think I did well on 3, ok on 1.5 and bad on 0.5. The average level of questions on a scale from 1-5 was a 4, 5 being the toughest, and I thought me doing good/ok in 4.5 was enough for an offer. Although I should make it clear that I did use hints from the interviewers sometimes, but not always.

If you ask me why I think I wasn't given an offer, I would say it must have been a combination of me not being from an ivy league university, although I am masters in computer science from a within top 50 state university in US, with a near 4.0 GPA and I have around 5 years of work experience. Or it could have been that I might have not paid attention to little details which I thought were not important, but they really were, like forgetting an obvious parameter while designing a method of a class which I quickly rectified once pointed out by the interviewer. Or it could have been that in all my solutions I started out with the most basic worst time complexity algorithm (because I didn't want to stare blankly at the whiteboard for half an hour thinking about an optimal solution), and over time improved it, sometimes with hints and sometimes without. But I have to say I was really proud of at-least two non-trivial solutions I came up with. This sort of uncertainty is exactly the thing that could have been avoided by a simple feedback email from Google instead of them just informing you on phone that you weren't good enough.

I hope your Google Interview experience wasn't like mine, but I would really like to know how it went for you?

Thanks.

Re: My Google Interview Experience

#3
Attention to detail matters. Spending time looking at the code, and talking about (and explaining) your solutions matters.

If an engineer misses details and won't spend time looking for a more optimal solution on a white board, I wouldn't expect them to do it in the day-to-day work of their career either.

Re: My Google Interview Experience

#4
My experience was similar to yours. I interviewed at YouTube, and I was flown over from New Zealand for the interview. When I returned the next day, I got my generic rejection letter with Dear {Full Name}. While I got the general solutions to the 5 questions throughout the day correct; I struggled to code them on a whiteboard with someone watching me; I can never think well in those situations when solving problems, but I find that the optimal solution clicks to me when I'm in the shower or wake up in the middle of the night.

It would be good to get some feedback about how to improve and where you went wrong. It's pretty hard dealing with a generic rejection after flying for 14 hours to the other side of the world for an interview! If the rejection is because of technical skill, then I think they could figure that out from a few more phone interviews (although I guess a free trip to the US isn't too bad).

I don't think it's because of the university though. One of my friends from NZ got a job out there and he was from my university, which doesn't have a particularly high reputation for computer science. I think he just knew how to nail the technical questions under pressure, and is more interested in algorithms and low level stuff than me, perhaps.

Re: My Google Interview Experience

#5

I have a phone call planned for next week about becoming an intern for my Year in Industry (during my third year at uni)... hopefully it will not require such a high level as yours did!

Personally the phone interview was much easier for me and I guess much lenient on any initially sub-optimal time complexity solutions, this doesn't mean you should relax though :). All the best for your interview.

Re: My Google Interview Experience

#7
I didn't make it as far as you did, I just had a phone screen. I was quizzed a lot about how I would set up a server architecture (something I've never done before) so my answers were obviously a bit basic. Then I was given two algorithms to describe. One of them I knew and described okay, the other one I didn't really know at all and did poorly.

I wasn't asked about any of my previous experience at all. I never felt like I had a chance to show off any of my skills and it didn't seem like they had even read my resume.

Re: My Google Interview Experience

#9
Having been on both sides, what the applicant often forgets is that you are being compared with the other candidates. It's not about reaching an absolute level. Maybe you were very good that day, but another candidate just was so amazing that she got the job. But you can't know, you just don't have enough information.

Re: My Google Interview Experience

#10

Having been on both sides, what the applicant often forgets is that you are being compared with the other candidates. It's not about reaching an absolute level. Maybe you were very good that day, but another candidate just was so amazing that she got the job. But you can't know, you just don't have enough information.

That doesn't really seem applicable. Google is more than big enough that they can hire both people if they are both good unless you're applying for a particularly specialized role which it didn't sound like was the case here.
Post reply on HN