4 ms·
I'd be interested to hear more about how you do that, and what you try to select for instead.
by kritiko 6y ago
I'd be interested to hear more about how you do that, and what you try to select for instead.
- gwbas1c 6y agoComprehension. Ironically, I just started writing a blog post about it 10 minutes ago. To summarize, I try and get the candidate to discuss tradeoffs between different approaches to common situations that the candidate should be familiar with. For example: Should GetUserById(int userId) return a null, or throw an exception, when there is no user with the ID? Explain the tradeoffs; or explain why each approach is better in different situations. Should you deserialize (xml or JSON) to a dictionary or a strongly-typed object? What if you need to manipulate the document while preserving fields that you didn't know about at compile time? Assuming you have the experience I'm screening for, you either know the tradeoffs or you don't.
- ativzzz 6y agoAny open ended question like > Explain the tradeoffs will benefit greatly from being able to synthesize a bunch of information out of some simple base. Yea you need to know the technical details but being able to explain tradeoffs is more abstract and the OPs method will just lead to a better answer here.
- twicetwice 6y agoExactly, yes! It's about explaining what you're thinking about as you think about it. Silence is a killer in interviews in my experience (not always—you can be strategic—but for the most part), and I try to minimize dead air in any interview I'm in.