Good stuff, and coincidentally good timing for me!  Thanks!

I definitely need to bookmark this list for the next time I interview!

I interview tomorrow and I am printing this list out so I don't forget. :-)

I think Joel Spolsky's list is pretty good:

(some overlap)

  1. Do you use source control?

  2. Can you make a build in one step?

  3. Do you make daily builds?

  4. Do you have a bug database?

  5. Do you fix bugs before writing new code?

  6. Do you have an up-to-date schedule?

  7. Do you have a spec?

  8. Do programmers have quiet working conditions?

  9. Do you use the best tools money can buy?

 10. Do you have testers?

 11. Do new candidates write code during their interview?

 12. Do you do hallway usability testing?

Dude, that sounds like a checklist for "I Only Want to Work for Big MegaCorp X."  Seriously.

I'm not arguing against any of those things listed -- they are *all* excellent, *all* things that any big megacorp should have in place 10 years ago.

I'm just worried that you are going to exclude a lot of exciting startup opportunities with this line of questions.  Early-stage startups have very small teams and bring up infrastructure as required.  Certainly, all of the things in your list should be aimed for.  Just don't expect them when you join if you want to be employee #15 at the next Google.

@Gary

I see a list of questions, not a list of expected answers.  These questions are useful in determining a potential employer's philosophy towards software development.  It is better to know more about the practices of a company before accepting a job than to find out later that you have major philosophical differences.

Ben Simo

http://QualityFrog.com

Good point however you should also define the job experience of the potential employee in your sector. For a Junior, new graduated employee; these are over qualified questions and I think it is not fair or for a foreign employee.

Would one of you be willing to share good answers to these questions? I would like to know what a best practices development shop should use and responds with to these questions.

Well its alrite

I've begun compiling a list of questions and discussion points for potential employers. Many of these

I've begun compiling a list of questions and discussion points for potential employers. Many of these

Pingback from  Tims Blog  » Blog Archive   » What about the links

Pingback from  “Questions every Candidate should ask a potential new employer” « Agile Software Company From Scratch

Pingback from  what questions should i ask a potential employer in an interview

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Pingback from  Jason L. Froebe: Ramblings of a Geek  » Blog Archive   » Questions to ask when you interview for a new job

One problem with asking these question is that you will unlikely get very honest answers, for example if you ask as in the last question above "Do you have documented coding standards, are they followed ?".

Then I do not believe that many potential employers would give you an honest reply such that "yes we have coding standards but virtually nobody cares about them".

A more likely answer would be a vague (and more or less dishonest) answer such as "yes we have coding standards, and we have some work to do before we can claim that everybody is following them completely".  

IMHO, a likely interpretation of such an answer is that virtually nobody is following the coding standards.

I would like to add a couple here.

Do you have a working area dedicated to programmers and not stuck in the middle of the accounting department?

Do your senior programmers have qualifications or are they self taught?

DT8YAt