3 ms·

At this point in my career (professional developer since the late '90s), I am extremely picky about who I work for. The interview is a two way street, where the

At this point in my career (professional developer since the late '90s), I am extremely picky about who I work for. The interview is a two way street, where the prospective employee also gets to ask questions to the potential employer. In the described workflow, the candidate must spend several hours before talking to anyone in depth at a company. This scenario would simply not work for me. I will not spend hours of my time for a company that I potentially might not want to work for.

jasonpeacock 13y ago
Would your rather that they have you come on-site and perform the coding challenge for half the day, then continue their normal interview process for the other half the day? Or worse, go through a normal 5-6hr interview loop doing random questions on the whiteboard? I think their approach is much more flexible and approachable. The overall time commitment is the same either way.
- donretag 13y ago
  You can achieve a mutual understanding during the initial technical (not HR) phone screen. This approach eliminates the candidate's ability to ask questions before a multi hour commitment. The traditional phone screen is important. Most questions cannot be answered by HR. I have a much better understanding a company after the question portion of a half hour phone screen than I can get from searching the web for information about a company.
at-fates-hands 13y ago
I'm completely the same way after getting burned early on in my career. I once did 5 interviews and several back-to-back code challenges for one company who in the end said, "Meh, we don't think your javascript skills are strong enough." I got this in a what amounted to a form email. You want code challenges? Check out my GitHub account and pull some of my repos and check my code. THEN call me if you still want to interview me. I'm at a point now where I've amassed enough code samples (apps, games, plugins, etc) that you should be able to determine if my coding skills are up to what you're looking for.
deleted 13y ago
[deleted]
RunForFun 13y ago
I also agree with this. When I interview them, my goal is to interview the client, and their goal is to interview me. If I am faced with too many impediments to reaching my goal, I will choose not to continue the interviewing process. Employers need to realize that the process is indeed a two way street and that they need to convince us that we should work with them as much as we need to convince them why they should want to work with us.

jasonpeacock 13y ago

Would your rather that they have you come on-site and perform the coding challenge for half the day, then continue their normal interview process for the other half the day? Or worse, go through a normal 5-6hr interview loop doing random questions on the whiteboard? I think their approach is much more flexible and approachable. The overall time commitment is the same either way.

donretag 13y ago
You can achieve a mutual understanding during the initial technical (not HR) phone screen. This approach eliminates the candidate's ability to ask questions before a multi hour commitment. The traditional phone screen is important. Most questions cannot be answered by HR. I have a much better understanding a company after the question portion of a half hour phone screen than I can get from searching the web for information about a company.

at-fates-hands 13y ago

I'm completely the same way after getting burned early on in my career. I once did 5 interviews and several back-to-back code challenges for one company who in the end said, "Meh, we don't think your javascript skills are strong enough." I got this in a what amounted to a form email. You want code challenges? Check out my GitHub account and pull some of my repos and check my code. THEN call me if you still want to interview me. I'm at a point now where I've amassed enough code samples (apps, games, plugins, etc) that you should be able to determine if my coding skills are up to what you're looking for.

deleted 13y ago

[deleted]

RunForFun 13y ago

I also agree with this. When I interview them, my goal is to interview the client, and their goal is to interview me. If I am faced with too many impediments to reaching my goal, I will choose not to continue the interviewing process. Employers need to realize that the process is indeed a two way street and that they need to convince us that we should work with them as much as we need to convince them why they should want to work with us.