The problem result is not the goal of the exercise, I don't care if you solve it, but rather how you approach it. Note that I don't use puzzle problems, but mo

The problem result is not the goal of the exercise, I don't care if you solve it, but rather how you approach it. Note that I don't use puzzle problems, but more open-ended ones that elicit discussion and architectural approaches rather than simple coding. When I'm interviewing I'm google for all intents and purposes. I want to see how you interact, what you're thinking and how it would be like working with you as a team member. I look for potential and red flags. I try to find out two main things: - will you be good for the team? - will the team be good for you? It's a two way relationship we're trying to build here. Interviewing is a lot like speed dating, we're trying to find a long term partner in a very small amount of time.