We had 15 resumes. 13 never made it past a phone interview.

What would have been worse for any of those 13 would have been if they *had* been hired. I think then the employer would have had a legitimate cause of action.

If I go in and apply for a job as an airline pilot with "Pilot" on my resume I better be able to fly a plane.

I can see putting your job experience in it's best light, but just stringing out a bunch of buzzwords on a resume is not to be recommended in a profession where it is very simple to tell very quickly if it is just bs.


>SNIP
>>I've seen Foxpro on resumes, but that is different than seeing apps on the screen.
>>
>>I was hired last year to interview/hire a VFP developer as an in-house developer entirely responsible for finishing and extending a pretty complex app that had been developed over 5 years by a programming shop. One guy who had VFP 3.0, 5.0 and 6.0 on his resume (along with Delphi, Powerbuilder etc). I asked him what he would do if he ran into a development problem he couldn't handle (fishing for UT, CIS, Hackfox) - he said he thought there was a Help button. I asked another "FOxpro Developer" about class libraries - he said when he went to junior college they had a library.
>>
>SNIP
>Charles,
>
>One has nothing to do with the other. Especially today, when people are told to put things on their resumes whether they really have the skills or not, the objective being to 'get the interview' and press on from there.
>I've seen it the other way too. A recent ad (about 6 months ago) wanted someone with a litany of disparate tool experience, include '5+ years of .NET'.
>
>That someone mis-represents themselves has nothing whatsoever to do with the actual number of people who DO have genuine FP/VFP experience.