comment on

The tales of covert evaluation procedures had me thinking for quite a while. I wondered how one could ever know how to react correctly. The whole concern irked me all along though - I passionately hate playing games like this.

My conclusion is that you have to decide on your goal: do you want this job, or are you looking for a job that's "for you"?

Since I decided that I want the latter, my answer is: I'd ask whether the interviewer is interested in comments on the code on the blackboard - it might be written by another interviewee who was rejected, f.ex, or be completely out of scope of the interview for a number of other reasons. If I'm given the go-ahead, then I wouldn't hesitate to mention my observations, just like I want others to mention theirs to me. If I'm then rejected for that reason, then it's not likely an employer I'd want to work for in the first place.

Makeshifts last the longest.

In reply to Re: An Interview Quandry by Aristotle
in thread An Interview Quandry by dws

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.


Your skill will accomplish what the force of many cannot
	PerlMonks