Guy kolbis

Eyal had recently been publishing interview questions. You can read all about them here.

When I was a junior developer, I went to some interviews that asked me questions similar to Eyal's questions. In some cases I knew the answer, in other cases I knew part of the answer and sometimes I did not know the answer at all.

Does it mean I am not a good developer?

Does it say something about me?

Am I not good enough?

At the time, it made me question my capabilities. After bad interview I did not have much confident at myself. Since those times I have grew and learned. I had evolved as a Developer, Architect,  Project Manager, CTO, Consultant and etc.

Speaking for experience, I must say that those interview questions really guaranty nothing. When I interview someone, I usually use a more common scenario and questions that are relevant to the current project we are working on. For instance, if we are developing a web application, I would ask for a simple web application that is connected to the database and displays something.

Having said that, in some cases those tricky questions will be valid but most of the time I prefer not using them. Instead, talk to the candidate, hear what he has to say and just "flow" with his knowledge and capabilities.

In my opinion, each candidate has different potential. You should not always use the same "template" and questions for each candidate.

What do you think?