I get handed a lot of resumes, and I developed a system to speed-evaluate the resumes.

• Quickly scan the recuiter's stuff, see if they have some personal stuff about it, but ignore the fluff about the technologies that the candidate used (according to them).
  Reason: They tend to put everything there. I suspect that the method they use is to ask a candidate if he every heard about SQL Server, and then put "Worked with SQL Server, Stored Procedures, Triggers, Indexes" instead. Perhaps they fail to understand the difference.
  I consider myself proficent in SQL Server, and I wrote two triggers in my life. There is no need to put stuff like this in every resume, it just end up being skipped.
• Go to the projects part, see if they have done anything interesting. Interesting being define as hard / rare. Usually, I search for doing stuff with multiply threads, AI, big systems, etc. No hard rule here.
• Languages, ignore any langauge that they know aside of C# and C++. C# because it is what we are hiring (although I have no issues with getting a VB guy) and C++ because I think that it is something that give tremendous help in understanding what is going on under the hood. I don't care what other langauges the candidate has managed to dredge from the bottomless pit of history. That they know HTML, JavaScript, VBScript, Ada, Pascal, and Shell Script is interesting for diversity, but doesn't influence decision otherwise.
• Technologies, don't really care about that. It is nice if they have experiance there, but we can just teach an emlpyee that ourselves.
  I am interested in seeing that they have a diverse background (at least it shows that they can learn well)

High notes:

• Mentioning unit testing, agile experiance or continious integration give a 10x of an interview.
• Working with open source software - just about any experiance with open source tools / frameworks is going to get a notice from me. The reason here is that it means that they manages to escape the evil clutches of Microsft Is The Source Of All Software mantra, which is at the very least very helpful.
• Being a member of an open source project - this one gets you an interview, period.
  This is not an altruistic move on my side, by the way. If you work on open source software it usually means that you are doing it on your own time. This, in turn, means that you care about the software. It also means that I can instantly see your code and check what kind of a developer you are. And, of course, that you are cofident enough in your abilities to make your code public*. It also makes you part of the community, which is very valuable.
• The candidate has a blog about software - also get an interview, period. For much the same reason that an OSS project does.

Sadly, I get a lot of really bad resumes / people. I would like to take this chance to announce again, if you are in Israel, and you are looking for a job as a software developer, give me a call or send me your resume**. Both my email and my phone are on the web site, and I would love to hear from you.

* As an aside, it also means that you probably don't suffer from "That is my code that you just touched!"

** And if I don't return to you within one day, it means that your email is in the spam folder or I'm dead. Try sending it again.