I've made similar tests for new employees, not for Perl but for other technical competency measurements. I don't use them in interviews, though.
I prefer to have a less formal interview. It should be a personal interaction so I can watch them think and react and formulate, and they can do the same of me. I may ask some technical issues and some political exercises (generic company politics, not world events).
However, I like to give this kind of test to a new hire. The test is a bit tougher and in-depth than the one you suggest above. I stress that they aren't expected to get everything right the first time, but they have a fixed period such as one month to become well-versed on the range of subjects presented. Some breeze through on the first day-- we usually knew they would. Some take the opportunity and time to learn what matters to the company-- we usually knew they would. Some demonstrate their deficiencies, not only in a lack of prior basics, but also in their inability to self-research and overcome gaps in their skillset.
[ e d @ h a l l e y . c c ]
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||