Actually, I used to work for a HR software company (go to the employment section at IBM USA and you'll be on their servers), and it is a numbers game once the company gets large enough or has a mass hiring binge.
From the company's perspective, they're getting resumes at 2-3 per minute (or faster), and there's no way for a human to look at them all. So companies set up workflows where the initial screening is done by the software, in an effort to reduce the workload on their recruiters.
Side note: We came across one guy in the database who applied for over 210 jobs at one client (caused some system problems for us, actually) -- everything from janator to CIO. Guess he
really wanted to work there.
So, your resume becomes critical not because it'll get you hired, but because it'll get you filtered out unless you can structure it in a way to make the filters happy.
So, always use plain text. Do not use these characters in it anywhere:
& ' " < > as many systems store or transfer data in XML, and those character entities commonly cause problems (not the systems I wrote, of course! But 3rd party vendors, etc.) Use a keyword summary section, where you list every keyword you think a filter might hit on for the items in your resume, plus common variations (acronyms, etc). And most importantly: check your spelling!
Chip H.
____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first