Hey I totally agree and look for very similar things when I conduct interviews for our company.
However I do like for the passion part when I see applicants that like to work on few personal, open source projects. But like you said yeah not looking to have someone doing commits everyday.
I also look for someone who is a team player and doesn't shut themselves out. We like to go (the whole team) drink and play darts on Fridays and I wouldn't want to hire someone who Friday night leaves everyday to go home and play some games for instance. (don't get me wrong I love gaming)
As much as I'm not a fan of whiteboard interviews, I still like to ask a few tech questions to see that I'm not with someone who has just wiggled their way through. I usually ask simple things such as: What is a recursive function? Do you know what the MVC model is ? How would you explain inheritance? etc.
For me it's really not about just finding someone who will code what we tell them to and do the job well and that's it. But really a discussion on finding what the person can bring to the team and how they will fit in.
I totally agree with this, and yeah, there definitely still needs to be some technical elements to the interview. I've tried both take home assignments and having a list of questions I ask during the interview, but I'm still trying to find a good balance. Team outings are also definitely a great way to build a stronger and more trusting team, and it's great to find a candidate who wants to participate.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey I totally agree and look for very similar things when I conduct interviews for our company.
However I do like for the passion part when I see applicants that like to work on few personal, open source projects. But like you said yeah not looking to have someone doing commits everyday.
I also look for someone who is a team player and doesn't shut themselves out. We like to go (the whole team) drink and play darts on Fridays and I wouldn't want to hire someone who Friday night leaves everyday to go home and play some games for instance. (don't get me wrong I love gaming)
As much as I'm not a fan of whiteboard interviews, I still like to ask a few tech questions to see that I'm not with someone who has just wiggled their way through. I usually ask simple things such as: What is a recursive function? Do you know what the MVC model is ? How would you explain inheritance? etc.
For me it's really not about just finding someone who will code what we tell them to and do the job well and that's it. But really a discussion on finding what the person can bring to the team and how they will fit in.
I totally agree with this, and yeah, there definitely still needs to be some technical elements to the interview. I've tried both take home assignments and having a list of questions I ask during the interview, but I'm still trying to find a good balance. Team outings are also definitely a great way to build a stronger and more trusting team, and it's great to find a candidate who wants to participate.