When I interviewed for my current position, I was handed a coding test. Turns out the previous applicant had "exaggerated" her ability to code in the language (Informix 4gl). References had not uncovered the gap in her technical expertise. She'd lasted a miserable 6 weeks, been unable to produce and was let go. After that fiasco, my company came up with the coding test. When I had to conduct interviews for a LAN manager position, we were asked to take one of several internal candidates. None of them were doing IT work for a living, so I came up with a list of interview questions that tested knowledge and expertise. I used references to evaluate the "soft" qualifications that I valued: communication, motivation, professionalism. It worked very well and I'll use the same combo again. Test for the technical skills, get references for the people skills. And get them before the offer is extended.
Dave
-
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.
|
