We do this, too, if the candidate has something they can show us. As someone else mentioned, this isn't always possible.
For what it's worth, we had someone come in a few weeks ago. Their code sample was pretty good, but there were things I'd have done differently, and, I think, better. But when he explained the code to me, not only was it clear he'd thought carefully about how it was supposed to work, but he had a solid explanation for every design decision. Based on that interview, I thought he should get an offer right away, test be darned. Sadly, after driving down for that, he decided that he didn't want to take on the commute that working for us would require.
And even if he was willing, I'd still have had to give him a test, because that's what management demands.
-
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.
|