• What is your dress code?
  • What are your hours and break policies?
  • Is there a probationary period with this job?
  • What is your policy on refactoring?
  • Do developers ever need to make changes directly on the production machines?
  • Where are your business rules? Are they lost in a gaggle of if-thens? Are they documented and tested? Have they been discussed and developed via interplay between business and technology?
  • Business actions or database actions? Are you directly using DBI in your application? Is there any direct evidence of the storage technology at work in your application code?
  • Where is your SQL cataloged? Do you use stored procedures and/or a module like Class::Phrasebook::SQL, SQL::Catalog, DBIx::SQLEngine, or Data::Phrasebook::SQL?
  • Is there any issue with me running xemacs everywhere I am expected to develop?
  • What database are you using? What motivated that decision? Are you happy with your decision?
  • How do you separate presentation control from business logic? For example, if your presentation is controlled by Template Toolkit, how does it source your business rules? Please don't tell me your business logic is enmeshed with your presentation control.
  • When I am supposed to fix a bug, do you want me to strengthen the code as a whole by refactoring or do you want 100-million bandaids and if-thens patched right over the problem? Where I work now, the answer is the latter.
  • Is X-Windows available on the development boxes?
  • Does your DBA (I'm assuming you have one) ensure that the databases in QA and development are refreshed regularly and completely?
  • Do I have my personal web server for development work or is everyone in the dev team using the same front end? Do I have my own database image?
  • What version control system do you use?
  • How frequently are changes from development released to production? What is the flow of such changes?
  • Does one change in the dev code for QA mean they test only the parts of the UI they think it affects? Or do they re-test the entire framework?
  • When a bug is submitted are the submitters aware of information required with each bug? Ie, if it is a UI bug, are they required to give a precise and complete series of navigation steps along with screenshots?
  • How does your web application handle authorization and authentication?
  • What do you use for application configuration?
  • What is your policy on CPAN usage?
  • Do we have our own CPAN archive?
  • How often do you update the version of Perl?
  • What books do the other members of this team read regarding Perl? Which mailing lists/newsgroups will I see posts from them on?