I need some tricky things
That's the last thing you need. You shouldn't be trying to trick applicants with obscure questions during interviews. Instead focus on the important areas:
- Look for a language independent understanding of programming, not just 463 ways to use unpack. Afterall, Perl isn't the best tool for every job, and even when it is their code will still benefit from the knowledge.
- Make sure they know the basics and can find the answers to more detailed questions if they're unsure. For example, ask them to write code to access a database, let them view the DBI docs if they haven't done this before.
- Look for code reuse. Ask them why they wouldn't write an XML or HTML parser in Perl from scratch.
- Get them to write some code, ask them about its maintainability and security.
The list goes on. As larsen noted, check out (OT) Interview questions -- your response? for many more good approaches.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||