4 ms·
> I've found that a standardized interview with asking the same questions to each candidate helps me better see the differences between candidates Oh, I start
by sho 8y ago
> I've found that a standardized interview with asking the same questions to each candidate helps me better see the differences between candidates
Oh, I start with a standard list of topics, and of course technical questions need to be consistent across interviews to be any use. But beyond that I like to let the interview flow naturally - if the candidate seems particular passionate about one thing or another, follow up on that, and see where it goes. It's a conversation, not some form to be filled out. If you're going to do that, may as well just email them the actual form.
Maybe the author isn't as strict as I understood but I really do believe that it's in that conversation that you get to know someone's personality, what they're passionate about, how they might fit culturally and how their experience and talents might complement the team. You don't get that from a survey.
- tchaffee 8y agoI agree with you about letting the interview flow naturally. That's how the last half of my interviews go. Often times looking at and discussing some of the candidate's code, depending on what the role is. I don't always get it perfectly right, but when I do my interviews feel good to both sides. It just feels like we spent an hour discussing a topic we both like and we both learned something new. > Maybe the author isn't as strict as I understood I didn't get the idea that he is when I read it. What I did get is that he wants lots of data points confirming the same thing. A list of standardized questions or topics is just one of those data points, right?