Re:Data structures and algorithms I actually used while work...
by jiggawatts on Wednesday July 15, 2020 @06:41PM
(#23853230)
They're doing it so that they can see your edits live, "prooving" that you're not cheating in some way.
But yes, this is asinine. Sharing your desktop through a video conferencing program and using the IDE of your choice would be far more realistic test, but Google likes to put hoops up to jump through that are smaller than your body.
Why can't you contort yourself like an octopus!? Fail!
Re:Data structures and algorithms I actually used while work...
by joshuamorton on Thursday July 16, 2020 @04:09AM
(#23856872)
Nah, it's because this is the process for phone, not video, interviews, which are somewhat more accessible. And you need the ability to record the code at the end anyway (which docs provides and a video doesn't).
Re:Data structures and algorithms I actually used while work...
by ladberg on Wednesday July 15, 2020 @08:26PM
(#23854252)
Yep, it was a struggle even when I thought I was supposed to be writing pseudocode. I've had some really great interviews using coderpad and similar software (including the company I'm at now), and it's such a better representation of how the interviewee actually codes.
I don't get how my interviewer (an engineer), didn't see the problem with it. I know that Google wants to use their own products, but that can't possibly be the norm for other Google interviews.
And yet somehow interviewers think that this will give them a good picture of how you'd do work on the job. Baffling.