We lost candidates due to recruiter screens like this when I was at Google. Not sure why they persist in doing them http://www.gwan.com/blog/20160405.html …
-
The HN comments have Google employees who claim it's implausible this ever happened to anyone, along with employee who says it's common.
Plus many people who claim similar experiences. Funny how often "works for me" turns into "couldn't possibly have not worked for anyone".
-
-
BTW, policy mandated gdocs for phone screens. Code editors like coderpad, stypi, etc., weren't allowed. I wonder if that's changed.
-
On the bright side, at least it's better than the Amazon intake process! https://rajk.me/amazon-interview-experience/ …pic.twitter.com/7feWbU9w86
-
Round 2. In round 3, you join a replication of the Milgram obedience experiment. J/k, R3 is the job; it only looks like a Milgram experimentpic.twitter.com/tAhg6zIPzZ
-
This is what happens when I refer someone to Microsoft without also forwarding them to a specific hiring manager http://moderndescartes.com/essays/my_ml_path …pic.twitter.com/cY0M5cv7Wm
- 1 more reply
New conversation -
-
-
time for the last stage of Bug Acceptance, "How the hell did this ever WORK?"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@garybernhardt Developer psychology again flat mapped on to organizational phenomena.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"on transient errors retry with exponential back-off" technique is required at Google more widely than I expected
-
except next attempt is at least in a year
- 5 more replies
New conversation -
-
-
Also known as “it’s impossible across time and space.” It’s a classic.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.