2 ms·
I feel like the whiteboard coding interview happens not because we want to put them in a hot seat and create a reality show, but rather that there is no other "
by dheera 8y ago
I feel like the whiteboard coding interview happens not because we want to put them in a hot seat and create a reality show, but rather that there is no other "obvious" way to test their coding skill in a short time.
Usually with whiteboard code interviews I focus on concepts and ability to break down and solve a problem, and don't focus on syntax or other things that I know they could figure out in 2 seconds from Googling. For example in C or C++:
* While I won't care if they forgot which #include was needed for a particular function or if they invent their own hypothetical string class with usual plausible methods, or if they wrote "v.append" instead of the correct "v.push_back", it is important to understand when and why memory leaks happen.
* It's reasonable to assume certain components exist in order to piece them together to create a higher-level task. If the task is to multiplex data from 3 sockets and de-multiplex them on the other side, for instance, it's reasonable to assume that a good socket library exists and assume some methods; I'm more interested in the multiplexing logic.
That said, I'd love more feedback about how to structure an interview in a better way to test software engineering ability. A lot of people say "whiteboard interviews are bad" -- and I agree -- but they don't really offer a good alternative. I'd love to hear what the good alternatives are.
- avgDev 8y ago"I feel like the whiteboard coding interview happens not because we want to put them in a hot seat and create a reality show, but rather that there is no other "obvious" way to test their coding skill in a short time." I totally disagree with this. In my experience I can tell if someone is familiar with a topic by asking a few relatively simple questions. You can't just make up shit about a framework/language if you never used it. There are practical things developers learn that someone will never know unless they did it. For example, if someone claimed they used Entity Framework with code-first and db first approach. I could simply ask them how they protect data annotations from being overwritten when updating the model in the db first approach. They can do so by using partial classes, anyone with a year of experience would know that if they used db first. Edit: Actually, I see your point too. Testing actually coding skills won't be solved by my example. It will only test particular knowledge and not any ability to actually solve the problem. However, in my area of work it's mostly creating CRUD applications that solve some business problems. I can't remember last time I wrote anything resembling an algorithm.