Imagine that you've been through two rounds of interviews for a job that involves some Perl coding. The first round includes a technical screen. You're given a whiteboard marker, and asked to sketch a solution to a fairly basic problem (one that gets at whether you can do simple stuff, like basic I/O, regular expressions, and some data accumulation and presentation using hashes.)
You pass the first round. You later hear that many prior candidates have crashed-and-burned during the technical screen.
In the second round, during a non-technical screen, you're back in the same room. You notice on the way in that the code now on the whiteboard isn't yours. During the course of the interview, you glance at the board a few times, first noticing that there is one outright bug, then that whoever wrote the code didn't understand autovivification, and then that they made a minor gaffe in a regex.
Do you point these problems out to the interviewer? Why (or why not)?
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, details, 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, summary, 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.