Flustering/stressing out candidates in an interview is not
always a bad thing, though. I guess it mostly depends on
the job that you're interviewing for. If it's for a sys
admin or webmaster or programmer who will have to quickly
fix broken production systems, I'd want someone who can think
on their feet. I'm not a fan of finding out at a bad moment
that someone chokes up & can't hack together code when
they're stressed. So there's no point of unnecessarily
stressing out every interview candidate, but if it's useful
for making a hiring decision, I'm all for asking tough
questions that they might not know the answers to & getting
them a little stressed out. -- cat
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
