3 ms·

Sorry, but the thing that reeks of entitlement is Google's abusive "we can pass you from interviewer to interviewer, making you do anything we want for days, an

by SiVal 13y ago

Sorry, but the thing that reeks of entitlement is Google's abusive "we can pass you from interviewer to interviewer, making you do anything we want for days, and you'll take it because there are plenty more where you came from," hiring practices. If Google thinks they have the power to do what they want to a candidate, and the GP poster thinks he has the power to limit how much of his time he'll offer them, I don't see why he is the only one accused of reeking of entitlement.

Jabbles 13y ago
"making you do anything we want for days" Days? I believe the median is 5 hours. The decision may then take days... but that's not the same thing.
- Nursie 13y ago
  When I was talking to them I was informed the hiring process usually took around 8-9 weeks. First a screening call, then a phone interview, then sometime later an in person interview, then an evaluation day in a Google building with multiple interviews and talks with various parts of various teams, then they would let you know within a couple of weeks. Yeah, no thanks.
  - freyr 13y ago
    The process may span 8 or 9 weeks, but you'd probably actively spend about 8 or 9 hours. That's a couple hours on the phone, and 5-6 hours on site. Presumably, you expect to hold the job for next few years of your life, at a minimum. If you can't budget 10 hours of your time, and you can't wait for a few weeks for an answer, it just doesn't sound like you really want to work there. Unless you're in desperate need for a job sooner... then I'd understand better.
    - Nursie 13y ago
      I was unemployed at the time (I'd just moved back to the UK and was looking for work) and didn't fancy hanging around for 2 months, so there is that. But even if I was employed I'd be looking for an out much faster. I work with 4 week notice periods (max). A two month decision process is just messing you about. --edit-- I'll add that the work sounded uninspiring, the location wasn't ideal and I was trying to go freelance/contract at the time (successful within a couple of weeks) so their goals and mine were completely misaligned...
    - sopooneo 13y ago
      Except you're effectively budgeting ten hours divided by the probability you get hired.
    - jacalata 13y ago
      I only have details for two people going through their interviews, but one of them took about 16 hours of in person time, and the other involved flying out to a different city for a day of interviews after ~6 hours of phone screening + a clusterfuckload of email time (partly due to some monumental incompetence on behalf of their HR department: when the recruiter involved left they said they had to restart the entire process).
zaphar 13y ago
I work at Google. My opinions in this comment are my own and not my employers. Google gets thousands of resumes and they have to whittle them down. Some are easy to rule out just based on the resume. Others are easy to rule out in the phone interview. But a large amount of them make it to the full in person interview. Now Google could just take it as first come first served and hire the first people that look decent. Or they could set the bar really high and whittle the pool down that way. They choose to set the bar really high. They can afford to because they get so many applicants. As an employee I appreciate that. It means that every one of my coworkers is crazy smart. Any one of them can review my code and offer useful feedback. There are no unqualified developers that I'm aware of at Google and Google is a pretty big company so that's a little amazing. Out of thousands of developers there are thousands of amazing high quality developers. It's partially market driven. When you get as many applicants as Google does and you are as awesome a place to work as Google is then you can afford to set the bar as high as Google does. And make no mistake they set the bar very very high.
- smtddr 13y ago
  Hey there, I just want to say I interviewed at the Googleplex in June 2012 and it was an amazing experience. When I got the "rejection"(5 days later, which is standard in my experince), I didn't feel bummed or angry - I felt that I was defeated fairly in a challenging game of chess with people better than me. The programming questions I got weren't out-of-bonds ridiculous like I'm always hearing about. While the process took nearly 6hrs that day, it wasn't just for the sake of it. I had real discussions about real-world problems and I enjoyed it greatly. Those 6hrs flew by. Everyone should go through Google's interview process at least once; it will reveal limits that you didn't know you had. I'm a better person, career-wise, because of that experience. Also, I'm sure I was able to get the awesome job I have now only because I was still charged-up from Google-interview-preparing a few weeks before. P.S., I'm sure I was close. I got a lot of smiles, nods, "yup, correct" and organic conversation that didn't seem rehearsed and they seemed happy to talk about so I suspect I did better than they expected but just... not... quite there yet... compared to some other candidates.
  - kamaal 13y ago

by SiVal 13y ago

Jabbles 13y ago

"making you do anything we want for days" Days? I believe the median is 5 hours. The decision may then take days... but that's not the same thing.

Nursie 13y ago
When I was talking to them I was informed the hiring process usually took around 8-9 weeks. First a screening call, then a phone interview, then sometime later an in person interview, then an evaluation day in a Google building with multiple interviews and talks with various parts of various teams, then they would let you know within a couple of weeks. Yeah, no thanks.
- freyr 13y ago
  The process may span 8 or 9 weeks, but you'd probably actively spend about 8 or 9 hours. That's a couple hours on the phone, and 5-6 hours on site. Presumably, you expect to hold the job for next few years of your life, at a minimum. If you can't budget 10 hours of your time, and you can't wait for a few weeks for an answer, it just doesn't sound like you really want to work there. Unless you're in desperate need for a job sooner... then I'd understand better.
  - Nursie 13y ago
    I was unemployed at the time (I'd just moved back to the UK and was looking for work) and didn't fancy hanging around for 2 months, so there is that. But even if I was employed I'd be looking for an out much faster. I work with 4 week notice periods (max). A two month decision process is just messing you about. --edit-- I'll add that the work sounded uninspiring, the location wasn't ideal and I was trying to go freelance/contract at the time (successful within a couple of weeks) so their goals and mine were completely misaligned...
  - sopooneo 13y ago
    Except you're effectively budgeting ten hours divided by the probability you get hired.
  - jacalata 13y ago
    I only have details for two people going through their interviews, but one of them took about 16 hours of in person time, and the other involved flying out to a different city for a day of interviews after ~6 hours of phone screening + a clusterfuckload of email time (partly due to some monumental incompetence on behalf of their HR department: when the recruiter involved left they said they had to restart the entire process).

zaphar 13y ago

I work at Google. My opinions in this comment are my own and not my employers. Google gets thousands of resumes and they have to whittle them down. Some are easy to rule out just based on the resume. Others are easy to rule out in the phone interview. But a large amount of them make it to the full in person interview. Now Google could just take it as first come first served and hire the first people that look decent. Or they could set the bar really high and whittle the pool down that way. They choose to set the bar really high. They can afford to because they get so many applicants. As an employee I appreciate that. It means that every one of my coworkers is crazy smart. Any one of them can review my code and offer useful feedback. There are no unqualified developers that I'm aware of at Google and Google is a pretty big company so that's a little amazing. Out of thousands of developers there are thousands of amazing high quality developers. It's partially market driven. When you get as many applicants as Google does and you are as awesome a place to work as Google is then you can afford to set the bar as high as Google does. And make no mistake they set the bar very very high.

smtddr 13y ago
Hey there, I just want to say I interviewed at the Googleplex in June 2012 and it was an amazing experience. When I got the "rejection"(5 days later, which is standard in my experince), I didn't feel bummed or angry - I felt that I was defeated fairly in a challenging game of chess with people better than me. The programming questions I got weren't out-of-bonds ridiculous like I'm always hearing about. While the process took nearly 6hrs that day, it wasn't just for the sake of it. I had real discussions about real-world problems and I enjoyed it greatly. Those 6hrs flew by. Everyone should go through Google's interview process at least once; it will reveal limits that you didn't know you had. I'm a better person, career-wise, because of that experience. Also, I'm sure I was able to get the awesome job I have now only because I was still charged-up from Google-interview-preparing a few weeks before. P.S., I'm sure I was close. I got a lot of smiles, nods, "yup, correct" and organic conversation that didn't seem rehearsed and they seemed happy to talk about so I suspect I did better than they expected but just... not... quite there yet... compared to some other candidates.
- kamaal 13y ago