It’s pretty simple, I think; The cost of the problems of Google Doc fall on you, with a small cost on Google itself, and negligible cost on the decision makers in Google responsible.
PS: Couldn’t you just copy the code you wrote in an editor to the Doc? If not, this might be hidden upside: They can watch as people code on Google Doc (as far as I remember), but doing this with an editor is somewhat harder. (VSCode’s liveshare or using a TUI editor in a shared tmux session seem better solutions to me, but Google optimizes for the lowest common denominator.)
It’s pretty simple, I think; The cost of the problems of Google Doc fall on you, with a small cost on Google itself, and negligible cost on the decision makers in Google responsible.
Wouldn’t it hurt the signal-to-noise ratio in evaluating candidates?
PS: Couldn’t you just copy the code you wrote in an editor to the Doc?
Yes. To me the implication of this is that it’d make sense to do so. I’m not sure how it relates to your follow up point.
They can watch as people code on Google Doc (as far as I remember), but doing this with an editor is somewhat harder.
It’s pretty simple, I think; The cost of the problems of Google Doc fall on you, with a small cost on Google itself, and negligible cost on the decision makers in Google responsible.
PS: Couldn’t you just copy the code you wrote in an editor to the Doc? If not, this might be hidden upside: They can watch as people code on Google Doc (as far as I remember), but doing this with an editor is somewhat harder. (VSCode’s liveshare or using a TUI editor in a shared tmux session seem better solutions to me, but Google optimizes for the lowest common denominator.)
Wouldn’t it hurt the signal-to-noise ratio in evaluating candidates?
Yes. To me the implication of this is that it’d make sense to do so. I’m not sure how it relates to your follow up point.
There are options. http://collabedit.com/ is my goto.