News for hackers. Stuff that matters.
Re:Google interviewing process for software developer role i... by cflewis on Monday February 24, 2020 @12:59PM (#22406464)
Alright, so Mountain View is waking up now and you'll get comments from Googlers, so here is mine.

DISCLAIMERS:

1. I work for Google, but these opinions are mine.

2. Everyone at Google is expected to interview, but I no longer do, and have not for two or three years. I have a medical exemption because for anxiety. Trust me, I know just as much as any candidate how stressful it is to be in that room.

3. I interviewed candidates for software engineering jobs.

4. I was an intern 8 years ago and 7 years ago, then flipped to full time 6 years ago.

5. I _do not believe I would pass the interview process cold_. As an intern, I got to use feedback from my internships to count for half of the interviews I would normally need to take. This was clutch: I'm good as a software engineer but would tank most Google interviews. I studied hard and I took mock interviews with my team while I was an intern. I knew my way around the campus and the rooms weren't alien to me, so I felt more comfortable.

6. None of this is meant to be a defense or repudiation of the OP's experience, nor is it meant to be a defense of Google or Google's hiring process. It's just meant to offer my explanation of why things are they way they are (other people may have difference perceptions of course).

With all that out of the way...

I've never met anyone at Google who is under any illusion that the hiring process is where the company would want it to be if anyone in the process could wave a magic wand. Even 8 years ago this was true. From the outside looking in, the process is byzantine and the experience of the OP is not as uncommon as one would hope.

The only way to make sense of it in your mind is to pretend to be on the inside looking out. Think of the interviewing process as a result of a set of constraints:

* Constraint 1: Google skews very heavily for no false positives, thus increasing the number of false negatives.

* Constraint 2: Google wants to hire as many people as it can that meet the bar in order to grow the way it wants, and it gets an enormous number of applications each year. But "Google" the company still grounds out to actual people running the show, and juggling this enormous candidate load is unenviable at best.

* Constraint 3: Because of how many people are being interviewed and the high bar, each interviewer somehow need to judge a candidate's quality within just one hour. This leads interviewers to ask hard/really hard questions about things you likely won't ever code but candidates who did good in school (or were good at studying for the interview) would have a shot at. I would never do this as I don't think that's a good signal at all; I would always ask questions that were basically about standard coding. I'd even print out a sheet of code that worked but had a number of code health failures and would ask candidates to do a code review of it.

Google has two main goals:

1. Hire the right people.

2. Knowing that the false negative rate is so high, make sure the process is pleasant enough that candidates will come back again.

I think 1 is doing pretty well, 2 is not, and 2 is not because it's buckling under the constraints. I would always try to help on a micro-level by doing things like checking if the candidate needed water, food, bathroom, testing out the whiteboard pens and replacing the bad ones (if I was nervous and I found my pen wasn't working straight off, I'd be thrown for a total loop), giving them 5 minutes to recenter themselves quietly, whatever. But those micro-level interactions don't help the macro-level experience.

You can imagine many ways of interviewing that would be better if you didn't have those constraints. If I was CEO of a startup, candidates who passed basic screening would be given access to the code base and asked to work for a day or two on an open bug. That would give you signal on their coding ability, ability to see through the ambiguity in the bug, work through an alien code base etc. etc. It would be great. It isn't possible here because there's so many candidates to work through.

There have been multiple initiatives over the years to try and make the process better, each one small nudges rather than global overhauls to avoid rocking the boat too much. After all, the process does kind of work: I work with smart people who I like being around and have done across all the teams I've been on, so something is working in the results. I think interviewees can now use a laptop for writing code in a room, for example (don't quote me on it, I stopped interviewing before that).

So, that's that. I hope it helps in understanding things, at least.

Re:Google interviewing process for software developer role i... by christiansakai on Monday February 24, 2020 @03:31PM (#22408112)
Thank you for writing such a detailed response. I appreciate it as someone who had interviews with Google 2 times (first one pass phone but failed onsite, the second one failed on phone but that was primarily because I wasn't in a good condition mentally during that time so that was on me).

I've heard and witnessed a couple people that I know who actually got into roles at Google (also FB, Amazon) but were not technically strong (yes they interviewed as SWE). I did ask what kinds of questions they got and it seemed that they did not get hard questions. This range from L3 to L5 and I was quite shocked.

This makes me believe that FAANG seeks something else as well rather than pure DS&A skills. I don't know what those are, but can you give me pointers?

(I failed one Google onsite, one Google phone, one Amazon onsite, and now currently will face a FB phone interview)

Re:Google interviewing process for software developer role i... by cflewis on Monday February 24, 2020 @04:32PM (#22408669)
Unfortunately sometimes it's just the luck of the draw on who you got as your interviewer. Remember that it is expected for false negatives so it is totally normal to just apply again in a year.

The thing you can do to help yourself is to study; there are only so many problems you can be asked. Most candidates don't. That gets you a lot of the way there. I used "Cracking the Coding Interview".

You are doing the right thing in interviewing as much as possible; interviewing is a skill that you get better with with practice. _Always_ ask your recruiter afterwards where your weak points were. Again, people make the mistake of thinking that their coding skills are entirely correlated with how they interview; this is 100% false. People can interview better but be technically weaker all-round and get an offer, or they can interview poorly and be the best technical candidate in the world and be rejected.

I hope this is helpful, I realize all of this stuff is demoralizing. As I said in my post, I strongly believe I wouldn't have passed a full Google interview round. Sometimes you just need luck on your side, but the more you interview, the better the odds things fall into place.

Re:Google interviewing process for software developer role i... by christiansakai on Monday February 24, 2020 @06:50PM (#22409631)
Thank you for the answer. I've been studying a lot, Leetcoding like crazy but lucky cases like that just demoralizes me.

Anyway, I guess what I can keep trying is to roll the dice. Thank you for the answer, it motivated me.

Re:Google interviewing process for software developer role i... by kart23 on Monday February 24, 2020 @05:19PM (#22409038)
How did you get your internship? I relate to you on the anxiety part, I freeze up badly during interviews, and I was literally shaking for an extremely simple white boarding question for an on-campus job. I guess the mock interview part should work pretty well for me. Thank you for typing this up though, it gives me a lot of clarity into the whole process.

I got contacted by a recruiter a couple years ago, and I turned down applying for a summer internship this year just because I didn't feel ready and would rather not go through all the stress. Now I'm wondering if I'll ever feel ready, and the anxiety and stress just puts me off the whole process, and makes me question if its even worth it with so many applicants.

Re:Google interviewing process for software developer role i... by rimliu on Tuesday February 25, 2020 @08:53AM (#22413161)
Sorry, but the combination of the two main goals seems moronic. There is no way to have a pleasant process for anyone who happens to be "false negative".
Re:Google interviewing process for software developer role i... by cmonnow on Monday February 24, 2020 @07:02PM (#22409709)
it's the scrutiny part that is strange.

as human beings, we are expected to behave differently when others are watching us, than when we are alone e.g. why lock doors before changing dress, or why cover mouth when yawning, or why not swear in an office etc. Naturally, we don't speak everything we think, lest we air the dirty laundry.

Do you judge a building during construction ? Do you judge an author by his first drafts ?

Either judge the final product, or only judge the process, or only judge speed of execution. And if you want to judge all three, then leave the candidate alone and let them think in their underpants and smoke if that's what gets their brain juices flowing.

As it is, they want to judge your thought process, your final result, your speed, and your ability to perform when someone is standing over your shoulder. It's a bit silly, mainly because it's not representative of any real-life scenario. Candidates who are introverted (exactly the IT geek types they want to hire) would have a major anxiety issue with the scrutiny part of it.

Re:Google interviewing process for software developer role i... by tomnj on Monday February 24, 2020 @02:00PM (#22407176)
Regarding laptops, I interviewed once in person in nyc and once in Montreal a few years back: only one (in nyc) brought a laptop for me to use

Edit: only one interviewer, that is

Re:Google interviewing process for software developer role i... by walshemj on Monday February 24, 2020 @08:07PM (#22410055)
Why constraint 1 - given USA Labour laws