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)?

---

---

• 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.