[oksurewhynot]

It wasn't really a choice when I interviewed there. All but one interviewer had me write code in the chromebook, which was my least favorite part of the interview process. The trackpad didn't respond to my slightly dry erase covered fingers, the keyboard was weird, and the quasi hangout software it was running crashed a few times, one of which required a full restart. That might not sound like a big deal but in a high pressure/time constrained environment it was a bit of a nightmare. I was told going in that the chromebooks would be available as an option, but writing a few lines of code only to be told to stop and switch over to the chromebook (which had either gone to sleep or frozen), have the interviewer log in and select the correct session, then select syntax highlighting, then finally being able to start writing code doesn't seem very conducive to maintaining a train of thought.

[dmoy]

Tell your recruiter, interviewers are not supposed to force candidates to use chromebooks.

[oksurewhynot]

I thought about it, but the chromebook hang ups were not the deciding factor in my performance (I did extremely meh and am fine with that because I'm entirely self taught and to even get that far was really cool). There were other larger problems with the process that google should be fixing instead of dinking around with chromebooks (I'm assuming they were there so code could be reviewed afterwards, which makes sense).