People doing the recruiting don't know anything about
1. Programming
2. Programmers
3. What makes a programmer 'good'
4. How to identify a 'good' programmer
5. How to appeal to a good programmer
1. Programming
2. Programmers
3. What makes a programmer 'good'
4. How to identify a 'good' programmer
5. How to appeal to a good programmer
Just out of curiosity, how would you identify a 'good' programmer? What makes a programmer 'good'?
Cheers for your answers in advance.
You also may be interested in Joel Spolsky's views on what employers should be looking for in a programmer. It's at http://www.joelonsoftware.com/articles/GuerrillaInterviewing...
If you really want me to get concrete, here's the dirt on startups hiring troubles: they usually flub 4 and/or 5.
Programmers are wising up. Only a small subset of startups are worth their time, unless it's a lifestyle choice, so they're choosy. Even among the small subset of startups that are worthwhile, they're not necessarily adept at communicating what actually appeals to programmers.