Speaking as a hiring manager, a resume is still good to setup a basic framework. What has this candidate done (names, places, types of work), what do they find

Speaking as a hiring manager, a resume is still good to setup a basic framework. What has this candidate done (names, places, types of work), what do they find interesting to highlight, what kind of extra stuff can I glean? What's interesting to me is less the actual words on the page and more how you put it together. Some questions I am asking myself when going through resumes: * Does this person know how to spell and can they use relatively proper grammar? I don't care if you're "Just" going to be a programmer, I expect a certain level of ability to document and write English. (And yes, if you're clearly not a native English speaker, that is taken into account. I still expect you to spell well -- spellcheck! -- but the rest is more fluid.) * What is their organization style like? Did they convey the information in a straightforward, easy to parse way, or is it a complete organizational mess? * Did they mention any open source volunteering or projects they're part of? This is a strong indicator of someone who is proactive and engaged with the world. * Do they list code references? A Github or Sourceforge account would be ideal, but I'll take anything I can get. * Do they tell me about their hobbies? (I generally hope not.) If they do, what do I think about them and what that means about a person? (Note: it's not fair to judge someone by the fact that they are a fly fisher, but it's damned hard not to, so please: stop putting your hobbies on your resume!) * Do they list a bunch of accolades and Greek societies? If so, they probably value certain types of recognition more than others. (This isn't a negative, it's just interesting to note.) * Do they hop from place to place, or are they the type who has been at Google for 8 years? These aren't necessarily pros or cons -- it all depends on why they made the decisions they did, and how open the candidate is about things. Uhm, now I'm rambling. Anyway, hiring is hard, resumes are hard, but I still really enjoy reading them. I understand that I could get most of the same from a portfolio -- and certainly, someone's Github profile would give me most of this -- but I still like to see someone out of their element. Most of us are engineers, but sometimes we have to document or present and I really enjoy seeing how people handle those sorts of tasks.