News for hackers. Stuff that matters.
Re:An inside look at Google’s data-driven job interview process by hkmurakami on Wednesday September 04, 2013 @09:27PM (#6331646)
On average, Google takes about 45 days to hire.

This struck me as exceedingly slow (I know that my friend got an offer in 10 days start to finish, but he's probably an anomaly since he had multiple offers already).

Is this in line with other software companies this size? I also wonder if this varies with function.

That fifth person is a “shadow interviewer” who is simply training to conduct interviews for future job seekers, and that person’s analysis isn’t included in the decision-making process.

This is hilarious! It's just like the ETS (education testing services) that runs all the US based standardized tests.

Re:An inside look at Google’s data-driven job interview process by philwelch on Thursday September 05, 2013 @01:49AM (#6332397)
45 days seems exceedingly slow to me as well, based on my experience with another large tech company. Though I can't say for sure the end-to-end time of the whole process, we can generally get from an onsite interview loop to a hiring decision within 24 hours, and HR takes another day or two to generate the first verbal offer. So that's what, three days? As I recall it didn't take anywhere near 42 days to go from resume submission to onsite interview, either.

How on earth does any company take 45 days!?

Re:An inside look at Google’s data-driven job interview process by tomkarlo on Thursday September 05, 2013 @02:05AM (#6332441)
It's not really slow if the "time to hire" is the time from an inbound resume, to an outbound written offer (or even longer, an accepted offer). (A verbal offer is great, but nobody generally accepts a verbal offer, they have to sign some kind of agreement to formally accept the job.)

The screening process takes a week or two (14 days) and then you have to schedule an on-site interview loop, which can often take a week or two lead time (since many interviewers have to travel to SF, and you have to schedule the interviewers as well) and that only leaves a week or two at best to issue a formal written offer. I've seen it take a lot longer than in total at many good companies.

Re:An inside look at Google’s data-driven job interview process by philwelch on Thursday September 05, 2013 @03:09AM (#6332644)
> (A verbal offer is great, but nobody generally accepts a verbal offer, they have to sign some kind of agreement to formally accept the job.)

Well, you'd want to call someone on the phone and get a verbal OK before sending them the offer letter, right? From verbal to written shouldn't be more than a 24 hour turnaround.

So that's the day of the interview, the day after the interview to make the decision, and three more days (so the rest of the week) to generate and send out a written offer that the candidate may or may not have already verbally okayed. That's 5 business days, or 5-7 calendar days.

> The screening process takes a week or two (14 days)

14 days to look at resumes and do a phone screen or two? Maybe at maximum, if you have to bounce the resume between teams to find the best fit.

> and then you have to schedule an on-site interview loop, which can often take a week or two lead time (since many interviewers have to travel to SF, and you have to schedule the interviewers as well)

Why would the interviewers have to travel? Don't you interview people on the same campus where most of the interviewers actually work? Why would it take two weeks to book a couple of hours on k different people's calendars (hopefully most of them selected from a pool of size n >> k)? Sorry, I think that timeline is way too padded.

Re:An inside look at Google’s data-driven job interview process by tomkarlo on Thursday September 05, 2013 @04:00PM (#6336555)
No, it can be a long time between a verbal and a written, because the verbal offer doesn't contain all the compensation details and requires final sign off from whoever makes those decisions. In almost all the corporate jobs I've gotten, I got a verbal offer relatively quickly, but the formal, signed offer letter came a long time (anywhere from a week to a month) later because it required the signature of VP or someone similar.

Re travel: I meant that the candidate has to travel, and the interviews have to be scheduled with the pool of interviewers. The minimum time for this is generally a week, but usually it takes longer. Interviews are a significant / immovable commitment and interviewers are required to give notice if they can't make it several days ahead, which means they have to be scheduled well before that.

Re:An inside look at Google’s data-driven job interview process by wallflower on Thursday September 05, 2013 @12:58AM (#6332272)
> Is this in line with other software companies this size?

Large companies, yes. Not sure about software.

And the thing that struck me as Monty Python ludicrous is that no one from the actual team is interviewing you! Almost every large company and most smaller companies have you interview on site with your actual team members. Is Googlish really that strong a predictor of team fit?

Re:An inside look at Google’s data-driven job interview process by packetslave on Wednesday September 04, 2013 @10:07PM (#6331785)
This is hilarious! It's just like the ETS (education testing services) that runs all the US based standardized tests.

What is "hilarious" about it? How would you propose that new-hires learn how to interview?

Re:An inside look at Google’s data-driven job interview process by hkmurakami on Wednesday September 04, 2013 @10:29PM (#6331839)
Why would you throw out the new hires' interviews entirely at all? Why not use it, even if you give it a lower weight?
Re:An inside look at Google’s data-driven job interview process by mvgoogler on Wednesday September 04, 2013 @11:11PM (#6331959)
Shadow interviewers don't do a separate interview. They typically observe an interview done by an experienced interviewer and then write up feedback.

It is primarily meant to be a learning experience for the shadow interviewer. They will get to see the feedback written by the primary interviewer, and the primary interviewer will usually critique the feedback from the shadow interviewer.

The feedback from the shadow interviewer isn't actually dis-carded - it gets sent to the hiring committee, with the indication that it is from a shadow interviewer. It can be given less weight by the hiring committee members, but I've been on hiring committees where the shadow interviewer picked up on something that the primary interviewer missed that affected the hiring decision.

Re:An inside look at Google’s data-driven job interview process by hkmurakami on Thursday September 05, 2013 @03:38PM (#6336414)
ah interesting. So basically the article got it completely wrong (how am I not surprised? :P)