Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    If you're not giving a written test during the interview, you could be shooting yourself in the foot. I've had them at my last four employers and was often surprised at how simple some of the questions were. At one place, I was told that another candidate left without completing the test, crying. Commented Nov 20, 2010 at 0:17
  • 1
    I absolutely agree that a written test during the interview is the only way to be sure that your recruits really have good programming skills. But the main thrust of my answer is that developer skills alone are not sufficient to address the SO's problem. Commented Nov 20, 2010 at 0:21
  • Got caught by the editing timer. I completely agree that standards and review are necessary. We recently published a new coding standards document and combined with some new code review processes we've had far fewer bugs make it to QA. One if my next goals is to start an internal training team. Commented Nov 20, 2010 at 0:27