> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Don Hyde
> Sent: Thursday, January 10, 2002 2:20 PM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [PIC]: Programmer
>
>
> As a former teacher and with some experience at interviewing potential
> hirees for programming jobs, I would advise against a multiple-guess test.
>
> The only justification for multiple-guess tests is that in the usual
> classroom situation, the teacher's workload exceeds human
> capacity so cheap
> shortcuts are unavoidable.  I simply cannot imagine being so swamped with
> promising candidates that you cannot afford the time to examine a better
> sample of their work.
>
> In my experience, 90% of candidates can be eliminated with one or
> two simple
> questions, such as "Have you ever programmed a PIC before?"  It's amazing
> how bad a job headhunters do of screening applicants, so the first sort is
> usually really quick.  The worst part is feeling guilty about
> having wasted
> the applicant's time coming to your office.  Cut your losses and his by
> letting him leave as soon as you can see it was a mistake.  You
> should have
> talked on the phone first.
>
> Then, if you're lucky and have two or more worthwhile ones to choose from,
> give them an actual short programming assignment and watch how they do it.
> Do they ask intelligent questions about the ambiguous parts of your spec
> (they'll be there even if you don't intentionally put them there,
> you know).
> Do they approach the task in an organized fashion?  Do they ask for the
> appropriate datasheet, or do they waste time trying to pretend they know
> everything already?  Did your personalities clash so badly that you don't
> want to work with him?  And, finally, did he get the job done?
>
Don,

I agree entirely with what you say.  As I have replied elsewhere the idea of
the questionaire was just another yard stick in addition to the formal
interview.

The idea of a short programming assignment is a good one and would certainly
be of more use than a simple questionaire.  Does anyone have any suggestions
on what would be a good excercise to be completed in say no more than an
hour?  We don't have the time to be able to vet someone to go through the
whole design from the thought processes, flow charts and on to coding and
simulation!

Thanks

David

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body