what questions should I ask job interviewers?

Well 4chan, I've just graduated university and when I move up North I'm going to be looking for a job.

I'm one of those slackers who never bothered getting a job while in college, so I'm going to try to emphasize what I learned rather than the fact I have no references or "real world" experience.  I think I pretty much know what to emphasize and tout.

What I don't know is what to ask the job interviewer.  What sort of things should I look for in a company?  Most of the questions I have are related to a company's morals (stop laughing) -- for example if I have a feeling they'll have me work on DRM or "Trusted" Computing, I'll scratch out that company as one to work for.  Other than that, what other sort of information is good to get out of a job interviewer when I'm a job-newbie/programmer-journeyman?

>>10

As someone who interviews college students and recent college grads for my boss when he's out of the country:

1)  If you give a sugar-coated, bullshit answer we'll know.  We've heard it before.  About a dozen times.

2)  A willingness to state and accept a few specific, professional weaknesses is generally interpreted as a willingness to grow.  Don't overdo it, though.  Someone who claims to know it all generally won't get hired.

3)  Your first job is your first job.  Don't expect it to be your career-completer.  Odds are pretty good that you'll be laid off within 10-15 years even if you don't quit to go to greener pastures.  Use your first job as an experience builder and as a place to learn more/master your field.

4)  Don't equate admitting a lack of knowledge to being unwilling to learn (as >>13 apparently has).  It's important to let your manager know when you'll be playing a game of catch-up because it'll probably take longer for you to complete.  Remember that 90% of technology decisions are based on business reasons.  Your cost-to-develop is an input to that equation.