Why not just pair with the interviewee for half a day or a day? You will learn how they think and work and if you like them. It's a riddle to me. I've never heard from anyone actually trying it and not being happy with the insight won.
I'm a lot more interested in how someone breaks down an architectural problem than I am in how well they can implement heap sort on a whiteboard. The closer the interview is to real coding the more you learn. Of course, github is the real resume now.
Hiring Developers: You're Doing It Wrong
21–30 of 230 posts
Re: Hiring Developers: You're Doing It Wrong
#22Other people just never applied. I remember manning the booth at one of those college campus events and it was very lonely. I probably talked to three students that day. Nobody followed up with us. I even had the distinct feeling that students avoided eye-contact with us and made beelines for the booths of the big established companies.
In the end, our hiring interview process for interns was 'do you want to work for us? yes? you're in' and for full-time applicants it was simply non-existent. I think in the last three years we did not interview a single person.
I often wondered why that is but I have never found a good answer. In the end it worked out for us. The company was acquired by Google.
Still, I would have liked to have some applicants and interviews once in a while because I keep reading so much about them and I wanted to practice being an interviewer to avoid pitfalls as described in the article.
Re: Hiring Developers: You're Doing It Wrong
#23While at my last job I was tasked with being apart of the interview process. My favorite question was "how do you keep up with web technology and trends? (web development)" and I was surprised at how many people had no answer for that simple question. My response to my manager was "this dude wont work"
I've also has people tell me that they read the study guides for the Microsoft certification exams. I'm not trying to start an argument about the value of certifications. I think it is questionable though when asked how someone keeps up with the latest technology, they reply that they read books with content of questionable real world application, from a single company, that are updated every three or four years.
Re: Hiring Developers: You're Doing It Wrong
#24Re: Hiring Developers: You're Doing It Wrong
#25Depending on his answer, I know right there whether to end the phone interview, or fly him to the Valley so I can see him write code on a whiteboard.
Re: Hiring Developers: You're Doing It Wrong
#26My current system is: 1) Simple programming challenge ( 2) Casual discussion-style interview to get to know how they think and behave. 3) Short term contract with a predefined project ( 4) Full time hire with salary + equity.
Re: Hiring Developers: You're Doing It Wrong
#27Re: Hiring Developers: You're Doing It Wrong
#28I worked for a German startup too and our main problem was not vetting interviewees but finding people who want to interview at all. In the five year history of the company I think only one single person was hired who was not already friends with someone at the company. Other people just never applied. I remember manning the booth at one of those college campus events and it was very lonely. I probably talked to thre…
Re: Hiring Developers: You're Doing It Wrong
#29My current system is: 1) Simple programming challenge ( 2) Casual discussion-style interview to get to know how they think and behave. 3) Short term contract with a predefined project ( 4) Full time hire with salary + equity.
Re: Hiring Developers: You're Doing It Wrong
#30I worked for a German startup too and our main problem was not vetting interviewees but finding people who want to interview at all. In the five year history of the company I think only one single person was hired who was not already friends with someone at the company. Other people just never applied. I remember manning the booth at one of those college campus events and it was very lonely. I probably talked to thre…