Actually, at my company we prefer more complete answers. We often give detailed scenarios and ask how they would go about solving the problem. We also give them a 50 question test covering much of the basics.
The QA session should get their blood running enough to show their enthusiasm. We do put them through a lot, but we are very nice about it. If they don't like it, then they won't want to work for us and we can move on to the next prospect.
It's also important to note that we begin serious QA over the phone, before they ever come down. You can eliminate much of the 'lies' and 'exaggerations' before you waste a lot of anyone's valuable time.
-
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.
|
