Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by TeeJay (2309) on 2003.02.21 9:47 (#17353) Homepage Journal
    One of the things I have always been glad of is having a bunch of programs (of varying quality) available on the net that I have written.

    Surprisingly very few interviewers have more than glanced at it. I would be very surprised if you had time to read through 100's of lines of perl code.

    In the past I have done about 6 or 7 perl quizes during interviews, I think they are a quite good indicator of knowledge but are very limited - after all much of the time you only actually use a small portion of perl modules and functions.

    Asking an interviewee how to solve a particular problem is usually helpful too, not asking them to write pseudocode or perl but rather going through the steps of solving the problem - what modules and approach they use.

    This is all from an interviewee perspective though - I have had about 25 interviews in the past 3 years so I have seen quite a bit, many interviews have been shockingly bad - some interviewers got distracted by dogma and politics too easily. Remember that if somebody has come for an interview they have probably already thought about how they would fit in with your choice of technology - that they probably want the job otherwise they wouldn't have gone for it.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;