Interview tips
-
Ask them to bring a project/program/util that they have written and ask them to wlak you through parts of the source code, from that you'll know if they can cut code or not.
.net is a box of never ending treasures, every day I get find another gem.
norm .net wrote:
Ask them to bring a project/program/util that they have written and ask them to wlak you through parts of the source code, from that you'll know if they can cut code or not.
And after doing that you might want to ask them if they actually have the right to show a prospective employer the materials that they presented. In the US actual employees will not have that right to company materials unless it is specifically given by the employer. And many contractors will not have that right either.
-
norm .net wrote:
Ask them to bring a project/program/util that they have written and ask them to wlak you through parts of the source code, from that you'll know if they can cut code or not.
And after doing that you might want to ask them if they actually have the right to show a prospective employer the materials that they presented. In the US actual employees will not have that right to company materials unless it is specifically given by the employer. And many contractors will not have that right either.
jschell wrote:
And after doing that you might want to ask them if they actually have the right to show a prospective employer the materials that they presented.
You said employers, I've written a networking desktop application that is and looks professional enough to be sold by Microsoft. This has been written in my own time and not connection with my current employers. And anyway you are showing code not giving it away.
.net is a box of never ending treasures, every day I get find another gem.
-
jschell wrote:
And after doing that you might want to ask them if they actually have the right to show a prospective employer the materials that they presented.
You said employers, I've written a networking desktop application that is and looks professional enough to be sold by Microsoft. This has been written in my own time and not connection with my current employers. And anyway you are showing code not giving it away.
.net is a box of never ending treasures, every day I get find another gem.
norm .net wrote:
You said employers, I've written a networking desktop application that is and looks professional enough to be sold by Microsoft. This has been written in my own time and not connection with my current employers.
If it is your own code, you have no limiting contractual agreements with your employer (some employers require such contracts), and it does not reflect what your employer does then you can show it. Contractual agreements might include any of the following or more - Rights to anything you produce, regardless of industry - Rights of first refusal on anything you produce - Rights of no-compete within the same industry If you signed something then it is your responsibility to know what you signed.
norm .net wrote:
And anyway you are showing code not giving it away.
Wrong. It is intellectual property. You have absolutely no rights to it. Including just "showing" it.
-
Anybody got any? I'm actually the one interviewing a candidate to replace a programmer that I inherited. They were totally incompetent.They were hired by a non-programmer and enjoyed a good couple of years of being able to BS their boss who didn't know a thing about what they were doing. The stuff they got away with is just shocking. However, they were nice enough to resign (a few months after I became their boss) before we had to fire them. Now we need a replacement and I'm want to make sure I can weed out the crap and the clueless. Anybody have any magic questions that can really reveal if they "get it"?
I think you should find one or two guru/consultants to sit in on the application process with you. They can help you weed out the wannabees. Just make sure they aren't looking themselves, or they will pull the best applicant away from you. Another thing you can do is employ a company like brainbench to have a small test prepared for applicants to take, they can provide you with a report of the skill level of your applicants. I've had to do this a few times for some jobs I've taken. Good Luck!
-
Ask them to bring a project/program/util that they have written and ask them to wlak you through parts of the source code, from that you'll know if they can cut code or not.
.net is a box of never ending treasures, every day I get find another gem.
Personally, I've never worked in an environment where any code has been allowed to leave the premisis, but on another note,check out these tips from Joel Spolsky: http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html[^] NB: See those in Edinburgh at the Radisson for a pint or two tonight.:-D
-
Anybody got any? I'm actually the one interviewing a candidate to replace a programmer that I inherited. They were totally incompetent.They were hired by a non-programmer and enjoyed a good couple of years of being able to BS their boss who didn't know a thing about what they were doing. The stuff they got away with is just shocking. However, they were nice enough to resign (a few months after I became their boss) before we had to fire them. Now we need a replacement and I'm want to make sure I can weed out the crap and the clueless. Anybody have any magic questions that can really reveal if they "get it"?
Get through it without using the word "challenge", in any of its forms. It turns me off no end when people describe a job I'm offering as "challenging" -- if I need someone who can't do a perfectly do-able job without struggling, I'll scout universities, not advertise in the pro press.