5 ms·

Google is infamous for jerking people around in the interview process. I had a very similar experience, as did several people I know. They do it because they k

Google is infamous for jerking people around in the interview process. I had a very similar experience, as did several people I know. They do it because they know they can get away with it, but I do wonder if they have a backup plan if the lustre of working for Google ever fades, because it's an open secret that their interview process is a fucking nightmare for no reason.

billytetrud 5y ago
That lustre has faded already.
- newsyyswen 5y ago
  Yeah, it's probably been 3-4 years since I've heard anyone use the word "Xoogler" in a positive or unironic way. Darn the wheel of the world! Why must it continually turn over?
  - deleted 5y ago
    [deleted]
- SCUSKU 5y ago
  Mine (and the public's) growing awareness of surveillance adtech really has taken away from my desire to apply to Google or Facebook.
  - swader999 5y ago
    Restoring my faith in humanity ^^^
- axaxs 5y ago
  Yeah... reminds me of a past coworker. He spent weeks writing weird comments in code, then writing weird code to read comments. From the actual source files. Then when deployments didn't work, he said they worked on his machine the deployment must be broke. He was hired by FAANG less than a month later.
  - grp000 5y ago
    To solve the hiring problem that seems rampant in the industry, I propose for all resumes that get past the auto-filter, we just implement a lottery system. Maybe it'll be even more effective than the current method!
devnull3 5y ago
> fucking nightmare for no reason Absolutely! To add, the amount of nit-picking that happens is staggering. I was downgraded from strong-hire to lean-hire because: 1. I did not use classes in Python. That problem could easily be solved using simple functions. The feedback I got was "candidate does not know idiomatic use of modules & classes" 2. I did not use one of python's standard lib functions and instead I coded it myself (I could not remember it at that instant) 3. I could not spot a scenario in the first 5-7 min of interview. I eventually spotted it and coded it well within the time limit. Somehow I felt that I am supposed to feel grateful for lean-hire
- wwweston 5y ago
  > 1. I did not use classes in Python. That problem could easily be solved using simple functions. The feedback I got was "candidate does not know idiomatic use of modules & classes" Apparently they missed this classic HN discussion: https://news.ycombinator.com/item?id=3717715 https://news.ycombinator.com/item?id=3717715
- paganel 5y ago
  > The feedback I got was "candidate does not know idiomatic use of modules & classes" Many googlers probably haven't read this blog-post from some time ago [1]: "Python Is Not Java". I mentioned that at my first interview for a Python programmer job ~15 years ago, i got hired (truth be told the interview was for a small-ish startup, not for a behemoth like Google). [1] https://dirtsimple.org/2004/12/python-is-not-java.html https://dirtsimple.org/2004/12/python-is-not-java.html
- aix1 5y ago
  Did you choose Python or were you asked to use Python by the interviewer?
  - devnull3 5y ago
    I chose Python because its faster to code
    - 5y ago

billytetrud 5y ago

That lustre has faded already.

newsyyswen 5y ago
Yeah, it's probably been 3-4 years since I've heard anyone use the word "Xoogler" in a positive or unironic way. Darn the wheel of the world! Why must it continually turn over?
- deleted 5y ago
  [deleted]
SCUSKU 5y ago
Mine (and the public's) growing awareness of surveillance adtech really has taken away from my desire to apply to Google or Facebook.
- swader999 5y ago
  Restoring my faith in humanity ^^^
axaxs 5y ago
Yeah... reminds me of a past coworker. He spent weeks writing weird comments in code, then writing weird code to read comments. From the actual source files. Then when deployments didn't work, he said they worked on his machine the deployment must be broke. He was hired by FAANG less than a month later.
- grp000 5y ago
  To solve the hiring problem that seems rampant in the industry, I propose for all resumes that get past the auto-filter, we just implement a lottery system. Maybe it'll be even more effective than the current method!

devnull3 5y ago

> fucking nightmare for no reason Absolutely! To add, the amount of nit-picking that happens is staggering. I was downgraded from strong-hire to lean-hire because: 1. I did not use classes in Python. That problem could easily be solved using simple functions. The feedback I got was "candidate does not know idiomatic use of modules & classes" 2. I did not use one of python's standard lib functions and instead I coded it myself (I could not remember it at that instant) 3. I could not spot a scenario in the first 5-7 min of interview. I eventually spotted it and coded it well within the time limit. Somehow I felt that I am supposed to feel grateful for lean-hire

wwweston 5y ago
> 1. I did not use classes in Python. That problem could easily be solved using simple functions. The feedback I got was "candidate does not know idiomatic use of modules & classes" Apparently they missed this classic HN discussion: https://news.ycombinator.com/item?id=3717715 https://news.ycombinator.com/item?id=3717715
paganel 5y ago
> The feedback I got was "candidate does not know idiomatic use of modules & classes" Many googlers probably haven't read this blog-post from some time ago [1]: "Python Is Not Java". I mentioned that at my first interview for a Python programmer job ~15 years ago, i got hired (truth be told the interview was for a small-ish startup, not for a behemoth like Google). [1] https://dirtsimple.org/2004/12/python-is-not-java.html https://dirtsimple.org/2004/12/python-is-not-java.html
aix1 5y ago
Did you choose Python or were you asked to use Python by the interviewer?
- devnull3 5y ago
  I chose Python because its faster to code
  - 5y ago