3 ms·
Haha, so true. There was one interview with a company I did where they explicitly said not to take more than a few hours but actually gave you a few days to co
by shortoncash 9y ago
Haha, so true.
There was one interview with a company I did where they explicitly said not to take more than a few hours but actually gave you a few days to complete it. So I legitimately cranked something out as fast as possible in under 2 hours and actually achieved the task at hand. But, since it was just 2 hours, I didn't bother making a makefile or splitting stuff into multiple files, or I used shortcut APIs.
In the end, every shortcut I used to get the job done in 2 hours became their justification for passing. So yeah, don't actually do the job in 2 hours.
- ThePadawan 9y agoHad a similar experience at an on-site coding interview. I was handed a single file of about 5000 lines of code and told "please note down what you would improve, just everything from formatting consistency to architecture". I got through around 1000 lines in the given time (can't recall how long that was) and had to tell them "I found too many things wrong with it, here is the gist". I went on to work on internal architecture and code quality in that position. So yeah, not all tests are made to be passed with flying colors, and not all tests are made to be flunked. Anything in between will still give you valuable output.