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.

An interview quandry 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I guess it would certainly depend. The way the job market is right now, at least for me, it's dog eat dog and you have to to anything and everything to stand out as the cream of the crop.

    So, I say, if you left them with any doubt about your coding abilities, point out the error, it will strengthen your position and weaken whoever wrote the code. If your skills are not in doubt it's perhaps a little tougher call, but I probably would anyway, maybe it is their way of a test.

    A lot of the things I read about interviews stress being able to give the interviewer the impression that if you started today you could solve some problem they have today. I love it when they give you real world examples, maybe a problem they are currently trying to solve, and I'm able to give them some sort of solution. It proves that you won't need a couple weeks "ramp up" time to get going.

    That said, it would also depend on the mood of the interview, not all things are appropriate in all situations.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.