3 ms·
How does any of this prove they are a good candidate? All this proves is they can remember things. When coding all if not 99% of these questions are a 4 second
by dubcanada 12y ago
How does any of this prove they are a good candidate? All this proves is they can remember things. When coding all if not 99% of these questions are a 4 second Google away.
And most of them are also opinions which tend to lead to bias. "Oh this user doesn't like Xcode, while I only use Xcode, so nope to him".
- bvanslyke 12y agoThis was my first thought, too. "What is widget X" isn't a good question. Questions more along the lines of "When would you use widget X over widget Y" will lead to better insight about a candidate, and will show actual experience. In the same way, for normal CS questions, "Write a hash-table implementation" is OK but I think it's better go with a question where a good solution involves using a hash-table.
- martinni 12y agoAbsolutely a lot of these questions were general knowledge to any techsavvy guy. I strongly recommend this book called [Cracking the coding interview] by Gayle Laakmann. It's very details and in-depth, helped me prepare for all my interviews.
- CameronBanga 12y agoUnderstandable that these are mostly just trivia questions, my thought was that they should be a springboard (pun intended) for senior developers/managers prepping for a hiring interview, who may be a bit unsure as to what to ask. Any candidate who answered these in one sentence/work answers with little detail would definitely not be a strong candidate, IMO. But mostly a round up of "Here's some topics to maybe dive into and get to know an engineer better with."
- flyosity 12y agoWhat would be an in-depth, wonderful answer to the question of "What's a navigation bar?"
- tonyarnold 12y agoA bar, that navigates.