Why Most Resumes Fail |
||||||||||
|
|
Home > Articles > Why Most Resumes Fail April 30, 2009 Despite the dozens of books and thousands of articles about how to write them, the majority of resumes are awful, according to most executive recruiters. After a couple of decades in the search game, Mark Jaffe, president of Minneapolis, executive search firm Wyatt & Jaffe, is still amazed at how bad they are.
Jaffe’s firm receives about 200-300 resumes every week. The firm’s two assistants spend about a minute scanning each one. If they spot credentials that match a search, the resume winds up on Jaffe’s desk. Facts that stand out are impressive executive positions and prestigious high-profile companies (FedEx, Microsoft, Intel, IBM) or extraordinary educational credentials (MBA from Harvard or from the WhartonSchool of the University of Pennsylvania).
How many resumes reach Jaffe’s desk? Are you ready? “Fewer than two per week,” he says.
Please login/register to read the entire article.
sponsored announcements and special offers
You can do this!
Earn your master's degree in project management without putting your life on hold at GoUWP.com! Apply today at GoUWP.com for 100% online courses, 45 PDUs each. No entrance exam. University of Wisconsin- Platteville’s MS in Project Management is globally accredited by PMI. Combine academics and real-world scenarios for a 360-degree education. If you have a distributed team, what are you trying to achieve with Agile approaches? Isn't Agile more for co-located teams? There are eight key benefits to working in a distributed Agile environment. A new report from ProjectsAtWork looks at each of those benefits – and how you can achieve them.
Most business and IT executives agree that any company able to rapidly deliver software of high and predictable quality with minimum budgets enjoys a significant advantage. However, practical experience shows that the challenges associated with software quality remain largely unsolved. Download the white paper Uplift Quality with Requirements Driven Testing to learn fundamental principles of Requirements Driven Testing.
|
| ||||||||
|
| ||||||||||