A bit on the technical side:
- How is quality ensured?
I got answers ranging from (code) reviews, acceptance tests, to "our programmers are just awfully good in programming". That last remark was off course a good reason to run away screaming.
But mostly the interview will guide itself a bit. I always put my hobbies on my resume and one company was afraid of the fact that had hobbies: Quite often when a new version of a program was released on friday afternoon, hell broke loose and the programmers were supposed to sacrifice their friday evening and entire weekend. When I explained the use of unit tests and the fact that they could prevent hell breaking loose, they answered that I was not allowed to write them because "time did not allow it".
So maybe above question can be rephrased: How does the company assure there is no stress for the developers/DBAs and the company?
+++ Despite being wrong in every important aspect, that is a very good analogy +++
Hex (in Darwin's Watch)