Hacker News new | past | comments | ask | show | jobs | submit login

You need to ask questions that let them show off their full understanding of a system. People without organization skills will focus on one area and not explain the whole.

My favorite is to have someone explain to me what happens when a browser makes a HTTP request to a web URL, which has <insert framework and DB here>. Network guys will tell you all about the request and response, web developers will focus on the front end, devOps will tell you how all the pieces communicate, etc. My expectation is for someone to at least be able to give a high level of all those things, while also having detailed knowledge of some specific areas... and seeing how they choose to answer such an open-ended question tells you quite a bit about where their focus and attention lies.




Personally, I would answer that question by telling you how the HTTP protocol works because, in my mind, that's what you're asking for. If you're going to ask that question, I think you need to be more clear about what you're looking for. I don't think there is any value in interviewers being intentionally vague in order to test if a candidate can guess what they're thinking.


You presume I want a specific answer -- I don't. I want to know how they think about a system. In your case, you laser-focused in on 'HTTP'. OK, that tells me a bit about how you think. If you were to say the question was too vague, that also would tell me how you think. If you were to ask for more clarification, that might be a really good first response. There is no right or wrong answer. Interviewers don't always seek specific answers. I'd argue that the best interviewers never seek specific answers, they ask questions that help us learn who you are.


Or you could just ask them to specify like, "did you mean explain x or y?".


I do. That wasn’t my point, however.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: