Earlier quoted context omitted.
I had a similarly bad Google experience that I've talked about before[0] but will copy here: I was asked to do a task that eventually boiled down to a topological sort, and I thought the question consisted of recognizing that the answer was a topological sort and moving on because it was over the phone. However, that was not the case. The interviewer wanted me to code it all out over Google Docs, but I didn't remembe…
Standard disclaimer: everything below is my own opinion based on my personal experience, and I'm not speaking on behalf of my employer. > I thought I was done, then the interviewer said she would go go copy my code and compile it after the interview to see if I was right, which blew my mind. I've been interviewing at Google for nine years and have never done this. I generally don't think it's fair to ding a candidate…
Like thats how I would feel writing code into freakin google docs during a job interview...with Google.
Tie 1 arm behind by back as the synax goes wonky, I'm fighting the spacing, etc. etc.
Or put mario Andretti into a ford focus, then test his lap times, with 0 warning.
Yuck.