>> I'd hire the person provisionally, with the option to let them go at any >> time in the next 30 days with no notice. Then I'd assess that person's performance on the job.<<
I think this will only work for people who do not already have a job (maybe between consulting gigs or byproduct of a layoff or buyout), or need to take a chance to break into the business. Chances are, if you are trying to hire someone with solid experience at the position you will have to convince them to leave their current job. It is difficult to entice good people with a threat that within the first 30 days you could be waxed at a moment's notice <g>. Besides, most jobs in our business are at-will so you can let them go anytime you want for any reason. As you have pointed out the key is to see how the person would function in the role. First I evaluate their experience and talk to them about their past projects. I want to make sure they memorized their resume. I see if they are BSing their way through the interview. No matter what position I am hiring for, I design questions during the interview process to determine how they would function in the job I am hiring the person to do. In Michael's situation, I would first want to determine how the person would develop a test plan. Are they going to ask where the requirements are? Can they tell me the difference between a bug and an enhancement request? Can they develop a test plan to start, or are they going to hunt and peck their way to finding bugs? I would drop in a couple of scenarios and see how they would approach the testing of the product verbally. Depending on the results, I might give them an EXE to test and see how they go about breaking down the app. The best Q/A person I have ever worked with made it his goal to force at least one developer to breakdown in tears every day <g>. Our customers *and* our developers (with a couple of exceptions) appreciated this guy (nicknamed - Testing Sith) because the software was way more solid than it would have been if we did not have him around. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
