comment on

After the pre-screening interview, I would suggest to make them write a semi-trivial script in real time, that is, in the interview situation, on a prepared PC with the standard tools (editors etc.), for a standard problem situation that comes up in your domain (e.g., web script, DBI connector, traverse directories, etc.).

Look at *how* they approach the problem. Do they re-invent the wheel? Do they consult the online documentation? How do they use the tools provided (editor, debugger, ...). Which questions do they ask you about the problem? Do they make an "analysis" of your requirements? How do they react to this stressful situation? And so on.

Since this procedure is pretty hard-core (emotion- and time-intensive), you will probably want to make sure to limit the number of candidates invited, to make sure you have adequate time for this procedure (e.g., 30-60 minutes).

Just my 2 cent.

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

In reply to Re: Interview questions by clemburg
in thread Interview questions by zigster

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks