As Steve, and a few other commenters above, said: an interview is not a one-way questioning. A job is a relationship and it goes both ways. Over the years I have developed a questionnaire of sorts that I ask when interviewing to ensure that I find a place that is right for me and helps me avoid situations that I did not like in the past. I try to get a sense of what the company does that I have found in the past is good for me and if they don't do things that I have found don't work for me. And some questions are just to get a big-picture view of the company, such as what health-care plan they have, do they do PTO vs separate sick & vacation days, how many vacation/PTO days, etc. Nobody should accept a job where they only know what the website tells them of the general terms of what the company does; an employee is not a customer and needs to know a lot more than what the PR department put on the website.

And as someone responsible for co-conducting interviews, I do ask everyone at the end of the session if they have any questions. And I certainly make a note of when a candidate does not ask any questions as it indicates a lack of being truly and deeply involved in a decision that has impact on their life. The way I see it is: Database Programming is highly detail-oriented and if a person is not going to interact with me, the interviewer, to draw out necessary details for making a good decision, then likely they will not interact with Project Managers and Developers (and others) to draw out details pertinent to the projects they are working on. Data Models are much harder to refactor than app code, especially after they get into Production and data is going into them, so there is little to no room for making assumptions.

Take care,

Solomon...