4 ms·
The biggest WTF I got out of this was: Writing code and tests in a Google Doc. I can't think of a much less friendly environment to write code in, except perha
by falcolas 7y ago
The biggest WTF I got out of this was:
Writing code and tests in a Google Doc. I can't think of a much less friendly environment to write code in, except perhaps Notepad. I did it once (for an intra-company interview), and it was nasty to deal with.
The WTF in second place was a blind requirement to know the mechanics behind a somewhat niche game that was big two years ago.
- pysxul 7y agoI was in the same situation. I simply asked if I could use intelliJ instead and then copy-paste everything in google doc at the end. The interviewer was ok with that.
- francisofascii 7y agoA Google doc certainly beats coding on a whiteboard or a stack of printer paper.
- dijit 7y agoA whiteboard isn't auto-"correcting" me and capitalising my start of lines though.
- francisofascii 7y agoTrue. The Google interviewer should have those two settings turned off.
- _throwawayyyyyy 7y agoone of my in-person interviewers at Google forgot they had to do this - I spent like 38 minutes of our interview whiteboarding and then he said, "oh crap you're supposed to do this on the computer" - i furiously typed for a few minutes to try to replicate what i'd done. when i later talked to HR there was no mention of this in the interviewer's report.
- Traster 7y agoCan you imagine working with that guy though - "Hey guys, I'm just about done with this feature get ready for the PR". "Paul, you've written it all on the whiteboard again. How many times Paul, it's got to go in the computer."
- blackflame7000 7y agoPaul throws 100 page manuscript of code into trash and walks off
- koonsolo 7y agoIt's of course better to blame you than to admit his own mistake. This reminds me of a joke at my previous job, where we always said "the intern did it" when something was wrong :D. The intern that already left months ago of course.
- Pinckney 7y agoThat really sucks. They're supposed to just take a photo of the board and transcribe it later. I never touched a computer when I interviewed. When was this? I think the chromebooks are fairly new in interviews, and it sounds like the interviewer didn't read the memo about how it works.
- yifanl 7y agoFunnily enough, I had to do an on-site interview with my current company via the Mac notes app (one of the interviewers was remote and we needed a screenshare). Coding with auto-correct is... not sensible. Thankfully they were alright with pseudocode.
- PretzelFisch 7y agoI still have nightmares using Doc as code editor. I new it would be bad, thought notepad would work as a good practice environment. But no Doc is like word tries to auto format/fix every line and tab. I couldn't deal with my code moving nor read it afterwords.
- dijit 7y agoOh god. the auto caps is just the beginning, auto-correct is not your friend. And they expected to be able to run the resulting code afterwards!
- wyclif 7y agoI'm curious, why wouldn't they let you just write it in Vim, Emacs, or even VSCode?
- PretzelFisch 7y agoWith google doc, they see you while you edit. There are other third parties that provide pretty good shared editors for this, but this is Google and tradition. I have always felt there 90% the interview process is a form of hazing.
- samatman 7y agoTo be fair, 2048 can be explained in a matter of minutes. The kind thing to do would be to demonstrate it. It's a different problem. I play a lot of 2048. It's on my watch, fun thing to do while stuck in line or whatever. I haven't the first clue how to write an algorithm to beat it. Here's how I'd do that: I'd get on the Googly-moogly and start reading up. Probably take me a couple days to get my bearings. In a 45 minute interview process? Forget it. They think they're testing for someone who can solve this problem. They're actually testing for someone who has encountered it recently in some other guise.
- eq_sd_ 7y agoI was asked to code 2048 in an interview at a major video game company. I don't necessarily think it's the most difficult thing ever, but I also don't think it's that easy if you've never even thought about it before. I knew I wasn't going to be able to completely solve it in 45 minutes and remarked solving it was more difficult than I thought it would be. The interviewer replied, "yeah, I tried it at home and thought it was pretty hard too." Seems like a pretty dumb question to ask in an interview unless you expect the interviewee to flounder.