News for hackers. Stuff that matters.
Re:My Google Interview Experience by cletus on Saturday February 25, 2012 @06:47PM (#3634242)
Hi,

I am a Google engineer and have gone through the process twice (the first time unsuccessfully). It can be a frustrating and even exhausting experience so I certainly understand why you're bummed it didn't work out (I was the first time) but let me clear up a few things.

You don't need to go to an Ivy League or otherwise top school (actually most of the Ivies aren't in the top CS schools). I certainly didn't. I didn't even go to school in the US.

As far as grades go, if you're going in with 5 years of post-school experience, your grades probably won't even enter into the picture.

As far as releasing interview scores goes, that isn't going to happen for good reason. A score, by itself, is meaningless. Interviewers are calibrated against other interviews they've done and other interviewers. This is all in an attempt to make a fair assessment of the candidate. If a particular interviewer gives high marks to candidates where all the other interviewers don't, that gets calibrated. And vice versa.

I would suggest that anyone who wants to apply have someone within the company refer you. For one thing they'll be able to guide you through the process better and (hopefully) set your expectations correctly.

Plus a strong internal reference will help you much more than acing an interview question.

Starting with a basic solution won't hurt you either. You're right that staring at the whiteboard blankly for half an hour is the wrong thing to do. More than the code itself, the interviewer is interested in how you think and how you apply your knowledge to find a solution more than the solution itself. A suboptimal solution that works trumps no solution or even a more optimized solution with serious problems. It's totally fine to start with something that works and then refine.

One question though: did you have five interviews onsite one after the other or was one of them a lunch (or was a lunch in between any of them)?

Feel free to contact me if you have any questions or simply want to pass along any feedback.

EDIT: to clarify the calibration comment, imagine interviewers give a grade to the interviewee. If a given interviewer gives nothing but A+s then an A+ means less from that interviewer. Likewise, all Cs makes another C not necessarily a problem. That's why I say individual feedback scores only mean something in context.

Also, what an interviewer writes about you means WAY more than any given score. An A+ with no justification is simply ignored. A C- with no justification is likewise ignored.

Luck can unfortunately enter the process in a way different to what you might expect. If we're hiring a lot of people then at that time it can be easier to get a "yes". If headcount is tight, it becomes correspondingly harder to get a "yes".

Lastly, there are two different answers wrapped up into "no" that you unfortunately can't distinguish between from the feedback you're given.

The first is a definite "no" in that we're sure that at least for now we don't want to extend an offer. You may simply not be ready. There can be lots of reasons. We may well re-interview such people a year or more down the track. A very few are definite "no"s (eg they became belligerent or wildly inappropriate--yes it sometimes happens).

The second type of "no" is simply "we're not absolutely sure it's a yes". I must've fallen into this category because I was contacted two months later. You may well be in this category. Unfortunately there's no way to know. But we do keep records of those that applied and constantly go back through them.

As far as acing all the interviews goes, no you don't need to but you probably need to do really well on at least well (and can probably bomb one). Of course all of this depends on the position, current hiring needs, the particular hiring committee you go through and a host of other factors.

Don't forget you're not being judged in isolation either. There may simply be a strong pool of other candidates at the time you applied.

Re:My Google Interview Experience by bmj on Saturday February 25, 2012 @07:42PM (#3634371)
I would suggest that anyone who wants to apply have someone within the company refer you. For one thing they'll be able to guide you through the process better and (hopefully) set your expectations correctly.

I want to underscore this. I have two friends (who didn't know each other), one who works at Google, another who applied at Google. The applicant had a similar experience (though he had two sets of phone interviews, since he wasn't in town), and he didn't get an offer. My Googler friend, however, was able to provide very good feedback, and the applicant walked away feeling motivated to try again in 6-12 months.

Re:My Google Interview Experience by zengr on Saturday February 25, 2012 @06:58PM (#3634269)
I remember your blog post[1] about Google interview. Love your answers on SO though.

[1]: http://www.cforcoding.com/2010/07/my-google-interview.html

Re:My Google Interview Experience by throwawayttt on Saturday February 25, 2012 @06:58PM (#3634268)
Thanks Cletus for taking the time to write that up. That really makes me feel better and provides somewhat more insight into the process.

My 5 years of experience was actually divided like 3 between Masters and Bachelors and 2 after Masters here in US, so I thought my Masters grade would matter.

My interviews were 3 before lunch and 2 after. Lunch was good :).

The interview conductor asked for references multiple times, but although I knew some people working in Google, but they had never closely worked with me, so I didn't want to make up references just for the sake of it.

EDIT: "As far as releasing interview scores goes, that isn't going to happen for good reason. A score, by itself, is meaningless. Interviewers are calibrated against other interviews they've done and other interviewers. This is all in an attempt to make a fair assessment of the candidate. If a particular interviewer gives high marks to candidates where all the other interviewers don't, that gets calibrated. And vice versa."

So what you are saying is that for me to not have made it through I must have equally messed all my interviews or at least a majority of them. I surely didn't feel like that after the interview, but who knows, since I still don't have a way to know if that is the case. Then this really sucks.

Re:My Google Interview Experience by mdwrigh2 on Saturday February 25, 2012 @07:47PM (#3634385)
> So what you are saying is that for me to not have made it through I must have equally messed all my interviews or at least a majority of them. I surely didn't feel like that after the interview, but who knows, since I still don't have a way to know if that is the case. Then this really sucks.

No, I don't believe that's what he's saying at all. All he's saying is that without knowing the past scoring of the interviewers, and the scores of other interview candidates, the numbers are meaningless. I could rate you a 6 on a scale of 1 - 10. This seems fairly average at first glance, but perhaps my median interview score is a 3. Now it's starting to look pretty good.

Nowhere in there did he say that you have to do poorly with all interviewers, or even most, just that they won't release numbers because without extra information those numbers are meaningless.

Re:My Google Interview Experience by jemfinch on Sunday February 26, 2012 @03:54PM (#3636746)
"So what you are saying is that for me to not have made it through I must have equally messed all my interviews or at least a majority of them. I surely didn't feel like that after the interview, but who knows, since I still don't have a way to know if that is the case. Then this really sucks."

Just a comment from another Google engineer who does interviews (and didn't do yours, since I haven't done any for a couple months now): your own feeling at the end of an interview may not at all reflect your actual performance in the interview, because you have no visibility into what questions weren't asked.

I like to interview candidates by asking them to solve a simple programming problem and then modifying the specification little by little, having them adjust their solution to implement new functionality. There are about 8 steps in my question, and frequently I'm gauging the quality of the candidate by how long it takes him to get through the first N stages; we fix bugs in earlier stages before moving on to the next stage. To calibrate myself, I've tried this question on several of my coworkers, and they were universally able to get about halfway through the question with bug-free code in about 10 minutes. Only one required prompting on my part to fix a bug. Most every candidate I've interviewed has taken 20-30 minutes to get to the same halfway point; by that time I've only got 15-25 minutes left in my interview, and the candidate seems so far like a "no hire", so I move to a different question to find out if the candidate has other strengths to counterbalance his weakness at solving this (simple) coding problem.

From the candidate's perspective, he only sees me ask a series of programming questions which he answers satisfactorily with a little prompting from me. If he answers another question or two satisfactorily, he may think he's done well, but he doesn't know that I wanted to delve more deeply into every question I asked him, and just didn't have time because the pace of his solutions was too slow.

I wish I could give this feedback to the people I've interviewed, but sadly, I can't.

Re:My Google Interview Experience by btilly on Saturday February 25, 2012 @10:36PM (#3634710)
So what you are saying is that for me to not have made it through I must have equally messed all my interviews or at least a majority of them.

You are talking as if the default is hire. That isn't so. The default result is not hire.

If a couple of people gave you mediocre results, you won't be hired.

Re:My Google Interview Experience by kjackson on Saturday February 25, 2012 @10:54PM (#3634749)
I would love it if Google spent some time re-interviewing a bunch of their current employees, to see how good their interview process is compared to random chance.

I know their best employees would likely pass the interview with flying colors, but my hunch is that there would be a large percentage of their employees that would fail. If they did a thorough analysis, my hunch is that their hiring process is likely determined by who their interviewers are, rather than who the candidate is.

I'm not bitter because I was rejected twice, but I do believe that their hiring process is a lot more random than what they believe it to be.

Re:My Google Interview Experience by alok-g on Sunday February 26, 2012 @11:17AM (#3635894)
I have interviewed over 100 candidates for my current company, thereby participated in post-interview meetings hearing other interviewers views on the candidate. I definitely feel that the selection process would fail many of the current, even some high-performing, employees.

I have no data-points for Google, but do recall an open aptitude test they had made available with a few problems so challenging that I felt nearly 100% sure that many of the current Google employees could not solve. Folks from Wolfram Research (the company behind wolfram-alpha) showed how to solve the problems [1] using Mathematica, their flagship product. (Turns out Google themselves had one of things incorrect!)

[1] http://mathworld.wolfram.com/news/2004-10-13/google/

Re:My Google Interview Experience by lutorm on Saturday February 25, 2012 @07:27PM (#3634330)
As far as releasing interview scores goes, that isn't going to happen for good reason.

This is true, but it sure would be helpful if they could give qualitative feedback like "the impression was that you were strong in a and b, but weak in x and y." That doesn't seem like too much to ask. (In fact, if he had good rapport with the recruiter I'm surprised that they didn't give that much information.)

Re:My Google Interview Experience by eta_carinae on Saturday February 25, 2012 @07:49PM (#3634389)
> This is true, but it sure would be helpful if they could give qualitative feedback like "the impression was that you were strong in a and b, but weak in x and y." That doesn't seem like too much to ask

Sadly, even this kind of feedback exposes the company on a legal front. There is a lot of precedent coming from rejected candidates who ended up suing the company because of this kind of feedback.

The only sane thing that a company can do from a legal standpoint is say "Sorry, we don't have a position for you at the moment, good luck in your search".

Re:My Google Interview Experience by lutorm on Saturday February 25, 2012 @09:03PM (#3634533)
Given how things work in the US, I guess that might be true. But on what grounds does someone get sued for saying "we don't think you know enough about template metaprogramming"? (that's less frivolous than getting sued for saying "we don't have a position for you at the moment", that is, since you don't need a reason to sue.)
Re:My Google Interview Experience by jonnyba on Sunday February 26, 2012 @01:12AM (#3634975)
A week later, the candidate discovers that the company instead hired someone else that happens to knows absolutely nothing about template metaprogramming. Except that person is whiter / younger / less married than said candidate.
Re:My Google Interview Experience by Drbble on Sunday February 26, 2012 @10:39AM (#3635804)
What does metaprogramming have to do with that complaint though? It is trivial to generate lawsuit without regard to feedback. Watch:

Does Google have family leave? --6 weeks, paid.

Did I get the job? --No

Because I plan to have kids??? See you in court!

Re:My Google Interview Experience by Drbble on Sunday February 26, 2012 @10:35AM (#3635796)
My company's was sued by a candidate because we offered him coffee and he glommed onto that as religious discrimination. There is no legal exposure from giving feedback. Some people will sue if they want, and some people will discriminate (and deserve to be sued).

Google reads your private email to "improve the product for you", why don't they want you reading their interview feedback so you can give them a better experience?

Re:My Google Interview Experience by velshin on Saturday February 25, 2012 @09:16PM (#3634556)
Am I off in thinking it's horrible for the interviewers to not provide feedback during the interview?

I'd also be curious how much throwawayttt probed for feedback during the interview process.

It always hurts to not get something you work hard for -- sorry mate!

Re:My Google Interview Experience by bhickey on Saturday February 25, 2012 @11:25PM (#3634811)
Imagine this from the perspective of an interviewer. Alice is interviewing Eve for a job at FooCorp. Eve rocks the interview. Alice is happy and gives Eve a high-five and some glowing feedback.

Then Bob interviews with Alice. Bob goes belly up. Never before has an interviewee done so poorly. Given the established precedent of providing feedback, what is Alice to do? We have a precedent in play. Would you want your employees telling candidates that they did a rubbish job? If she declines to tell Bob how he did, he'll interpret it as a negative. If she tells Bob that everything was dandy, it will set Bob's expectations.

The only reasonable choice is to bar your employees from providing feedback. Any other course of action is unfair to them.

Re:My Google Interview Experience by harlanlewis on Tuesday February 28, 2012 @10:04PM (#3646229)
This implies that feedback can't be provided throughout the interview. Reduce feedback loops, etc etc.

In some of the 'worst' interviews I've conducted, it would become clear with 45 minutes to go that the candidate was a pass for technical reasons. After exploring for other strengths beyond the expected skillset, I focus the rest of these sessions on the really important things the candidate should know before their next interview with some other company. This is easy to present as standard interview questions, but with more explanation and context worked in to setup and 'next step' in multiparty questions. With no explicit "you've failed" ever stated, you have an opportunity to maintain a positive conversation, do the candidate a service and a favor by educating on what they need to learn next, and if you're really lucky discover that the candidate is a fast and eager learner who would be a great addition to the team despite current deficiencies.

Worst case, it's clear to the candidate where they're lacking without ever needing to state is as such. And who doesn't learn a little bit themselves every time they teach?

Re:My Google Interview Experience by tytso on Saturday February 25, 2012 @10:03PM (#3634646)
For legal reasons, most employers will tell interviewers not to reveal any information at all about how you did. Unfortunately, the US is a highly litigious society, with lots and lots of lawyers egging people to sue over just about anything....
Re:My Google Interview Experience by velshin on Saturday February 25, 2012 @11:02PM (#3634763)
As an interviewer, to indicate things are going well, you can smile, nod, give happy words of encouragement, get excited, etc.

When things are going poorly, you can frown, say "not quite", give sour words of encouragement, linger on the same unsolved problem, etc.

While HR / Legal usually have policies prohibiting direct feedback ("You're a 5 of 10 and we have 30 candidates who are all better than you. Also you went to Yale and that's lame."), there are many ways to provide feedback to the interview candidate without opening the company up to legal trouble. There are no laws against being human during an interview.

Re:My Google Interview Experience by lamby on Saturday February 25, 2012 @07:33PM (#3634345)
> You don't need to go to an Ivy League or otherwise top school [..] I didn't even go to school in the US.

Because there are no good schools outside the US?