Reply to thread

Message

<blockquote data-quote="IronWolf" data-source="post: 3416624" data-attributes="member: 21076">You don't really mention your interviewing techniques, but is it possible you might be ruling out good candidates due to them?&nbsp; I've seen a lot of interviewers ask pointed, specific questions about a certain technology of people and rule good ones out due to that simply being an area the dev doesn't work in everyday.&nbsp; It might only take a good programmer a day or two to pick up the syntax and soon be up and running cranking out code for you.One of our programmer hires from about two years ago didn't have a lot of experience with what was going to be their first major project.&nbsp; But the folks that interviewed the candidate were more interested in the person's background and knowledge of design and theory than asking specific, pointed question in the language they were looking for.&nbsp; It paid off quite well.&nbsp; The person hired completed the project on time and there were no significant issues when the app was rolled into production (and it was a critical component of the system going into place).&nbsp; I am sure everyone has different experiences though and we may have just been lucky to get a good pick the first time.&nbsp; But it might be worth considering re-evaluating the interview practices to make sure you aren't inadvertantly ruling out good candidates.</blockquote>

[QUOTE="IronWolf, post: 3416624, member: 21076"] You don't really mention your interviewing techniques, but is it possible you might be ruling out good candidates due to them? I've seen a lot of interviewers ask pointed, specific questions about a certain technology of people and rule good ones out due to that simply being an area the dev doesn't work in everyday. It might only take a good programmer a day or two to pick up the syntax and soon be up and running cranking out code for you. One of our programmer hires from about two years ago didn't have a lot of experience with what was going to be their first major project. But the folks that interviewed the candidate were more interested in the person's background and knowledge of design and theory than asking specific, pointed question in the language they were looking for. It paid off quite well. The person hired completed the project on time and there were no significant issues when the app was rolled into production (and it was a critical component of the system going into place). I am sure everyone has different experiences though and we may have just been lucky to get a good pick the first time. But it might be worth considering re-evaluating the interview practices to make sure you aren't inadvertantly ruling out good candidates. [/QUOTE]

Verification