I hope that when you read these posts, you came to the same conclusion I did. It's almost impossible to detect from a resume whether or not a candidate is accustomed to an agile project, or could work on an agile project successfully. Keywords, especially, are useless when it comes to reviewing resumes.

So what's a recruiter or hiring manager to do? Look at domain expertise, glean what you can about the kinds of team the candidate has worked on, and develop a phone screen or an audition that you can use before the interview.

Phone screens don't have to take a lot of time. Sure they're inconvenient. One technique I saw at SD last week was the essay as a pre-interview assessment. Sure you'll still have to read the essays, but fewer candidates will write them, so you'll have fewer people to screen.

Phone screens and essays are time consuming and possibly inconvenient. But a bad hire is more than inconvenient--it's much expensive than any time you spend phone-screening or reading resumes.

The other posts in this series:

• Reviewing Resumes for an Agile Team: Start with Lifecycles
• Reviewing Resumes for an Agile Team: Look for Practices
• Reviewing Resumes for an Agile Team: Qualities, Preferences, Non-Technical Skills

posted by Johanna Rothman at at 8:03 AM | link |