[joshstrange]

There are sometimes “wrong” answers in an interview but I try not to ask questions that have a “right” answer.

For example: “Describe a production issue you dealt with and how you approached it”. It doesn’t matter what the issue was, how you fixed it, etc. I want to see that you _have_ dealt with a prod issue and also talk through how you solved it or how you debugged the problem.

In an interview I’m trying gauge how you think, how you will interact with me/the team, how you approach problems. If you can talk and explain your reasoning you are already ahead of the pack. The worst thing you can do is freeze up. Give me a stream of consciousness over freezing up any day of the week.

I often ask questions like “What do you think about X tech?” just to get you talking about it, not because I want you to say “I love it” or “I hate it”.