Quote:
Originally Posted by p1l0t
Yeah but bugs are normal part of the process that's why we do test. I'm not sure they are expecting you to debug in a live interview though.
Sent from my SM-G975U using Tapatalk
|
Most of the time they do expect it, in my experience.
I actually wrote this up on twitter the other day lol. But here's kind of how things go:
1. They say they want to know if you can write code that compiles and runs.
2. They want to know that you know your algorithms and data structures.
3. We want to test that you can work with people, debug code, pair program.
I've had a few interviews now where IMO I did all three. One of them the guy even told me "that's the approach and algorithms/data structures I would use", and for one bug he offered himself to double check it for me while I was focused on another part of the code. The code compiled and ran fine, got the correct results, etc. Then this week I got the rejection email.
