Ah, come on, it's not that big of a deal. I mean, I could nit pick stuff too:
"be good at you're job"
Know the difference between your and you're. When you make mistakes involving contractions, you're painting yourself in a really negative light; It's not just a simple spelling error.
Know when to capitalize something and when not to.
[...] negative light; It's not just a [...]
Or, even better: Make a 10 second [...]
My point: pointing errors out is fine, but give people the benefit of the doubt. For some reason I have an easier time accidentally adding/missing an apostrophe when I'm typing than when I'm writing, or mixing up to/too and similar words. I know the difference, and I notice it when reading if someone's missed them, but I think I type faster than I think and I mix things up.
Anyway, back to the original topic. I haven't read everything in this thread, and I wouldn't be surprised if others have said this, but a few of things I look for are:
- Commitment. I want people who are committed! A good sign of this is seeing work already done. This can be in the form of a nice logo/blog/website (simple, but professional looking), or it can be in the form of a demo/prototype.
- Down to earth. If someone says it's going to be the next WoW or Halo, I'm out. 'Cause it's not. People need to be realistic.
- Knowledgable. I'm not the smartest guy on the plannet, and I know lots of programmers who are way better than me, but I'm not too shabby, and I have absolutely no desire to drag un-knowledgable people through a project. This also extends to being able to learn new things well, because teams are always in a state of learning.