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 …
-
-
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
- 3 more replies
New conversation -
-
-
still the case. I wasted so much time compulsively indenting.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Had a different G interview with coding in gdocs. Nailed the problem, but the interviewer didn't like me, so there was no followup.
-
How could anybody not like you :o?!
- 17 more replies
New conversation -
-
-
NOPE. Did two screenings with them recently. Both were through google docs. No syntax highlighting, nothing.
-
Also, page breaks while writing code. lol.
End of conversation
New conversation -
-
-
lol, the only time I’ve had to type code in gdocs for an interview was with an ex-googler
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
nope! I screened there early this year and had to use gdocs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Interviewed there recently and it hasn't changed. Coding in gdocs is terrible and puts the interviewer at a disadvantage.
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.