All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

I've been looking for a new job recently. Here's some of the questions I ask:* What do you like best about working here? What do you like least? What would you change if you could?* How are conflicts resolved? Specifically, technical conflicts, interpersonal conflicts, etc.* How are business and technical goals balanced?* Do you think you're given reasonable goals? How are missed deadlines handled?* Do do automated testing? Do you have QA? Code reviews? Docs?* How would I fit in here? What do you see my rol

Which reminds me that one non-squirmy question I've asked is What version(s) of perl do you use? Now I might be a bit narcissistic for asking that one, but it does tend to reveal how much the person interviewing you really knows about the system, and about Perl. It reminds me of clkao's classic conference question, which he asked after every talk (until other people started joining in and beating him to it):

What version(s) of perl do you use? Now I might be a bit narcissistic for asking that one

Not at all. It gives you useful information, and reveals that you take your pumpking responsibilities seriously.

Additionally, if the employer is interested in you specifically because of your deep knowledge of perl internals, it lets you start a conversation with them about why they use the version they do, and the benefits and problems with that version related to the kind of programs they write.

Then again, I'm relatively new to the workforce, so I probably shouldn't be giving interview advice.:)