4 ms·

Sitting here, in your chair, you can definitely do this no problem, right? So find a group of people who will simulate the interview environment for you. Also,

Sitting here, in your chair, you can definitely do this no problem, right? So find a group of people who will simulate the interview environment for you. Also, there are strategies for managing the time problem. 20 minutes is a bit fast for understand => ask questions => implement => test on this problem. But you can organize the code so that if you run out of time it's still clear you knew how to solve the problem and can code your way out of a wet paper bag. E.g., I would pass an answer that got everything correct but didn't get around to implementing isPalindrome() or isSoCS() before the 20 minutes was up, especially if the candidate could give a ~1 minute description of how to implement those functions. (I would also give more than 20 minutes.)

perl4ever 8y ago
I interviewed at a place that started by having me do a HackerRank test online, and complimented me on my code and comments. Then the in person interview ended with a coding test involving a much simpler problem which I assume I failed, from my perspective due to the pressure of limited time and people talking at me. It's hard for me to figure out what was going on, unless they basically thought they were testing to see if I cheated on the first test. However, I haven't experienced repeated failure of a consistent type, so I'm not particularly motivated to worry about this sort of thing. I do know that different companies have radically different processes, so if someone tells you "you're not a good fit" it may be completely true and not a negative judgement at all (even if that's how they mean it). It so happens that I got my undergraduate degree about ten years later than is typical, and thus I can pass for someone that much younger than me, at present. So in an interview, it is tempting for me to give away my age by reminiscing about computing in the 80s, and that could have caused me to be rejected a couple times but I will never know for sure...

perl4ever 8y ago

I interviewed at a place that started by having me do a HackerRank test online, and complimented me on my code and comments. Then the in person interview ended with a coding test involving a much simpler problem which I assume I failed, from my perspective due to the pressure of limited time and people talking at me. It's hard for me to figure out what was going on, unless they basically thought they were testing to see if I cheated on the first test. However, I haven't experienced repeated failure of a consistent type, so I'm not particularly motivated to worry about this sort of thing. I do know that different companies have radically different processes, so if someone tells you "you're not a good fit" it may be completely true and not a negative judgement at all (even if that's how they mean it). It so happens that I got my undergraduate degree about ten years later than is typical, and thus I can pass for someone that much younger than me, at present. So in an interview, it is tempting for me to give away my age by reminiscing about computing in the 80s, and that could have caused me to be rejected a couple times but I will never know for sure...