I disagree here. Not only have I done technical interviews, but recently had a few (since I am moving I had a few interviews). I expect that people will ask a few questions (basic to advanced) on Perl to help guage skill level. You would be surprised at how many people have programmed Perl for a few years and don't know what CPAN is, or the difference between chop and chomp, or about ties, or anything you may expect them to know. At an interview 2 weeks ago (which I got an offer from, yay me!) one of the guys read an unpublished article I did on ties and he said 'Just to make sure you really wrote it, explain how you would write a package to tie to a database'. I was happy he did since I know the interviewer is doing their homework on me.

Something I like to do when interviewing is take a recent or current problem being worked on and ask them how they would solve it. This way you can see how someones mind works, as well as their technical ability since they may mention various modules or techniques in the process which will demonstrate their clue level.

So, to make a short comment long... I think asking strategic and pointed questions about Perl is a Good Thing when interviewing. If the interviewee is offended by it and leaves, then they were simply not a fit.

Cheers,
KM

---

---

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