@barney: "This is perhaps the most preposterous lie I've ever seen on a programming forum." You say that, without any basis, where I can affirm that this does and has indeed happened. It happened to me; twice. I was broke both times, didn't have a choice, and did end up getting the job and the first thing I was to do was clean up my interview 'test' code and implement it in production.

Jasmine, I'd like to ask a serious question: Are you skilled in all of those things (honestly)? When do you decide not to put something on your resume anymore? At one point, I've worked in/with all of those technologies (except oracle), but I can't say that I could be proficient with them if hired to do the job tomorrow. Heck; in half of them, if you haven't worked with it in a year, it's not the same anymore. It's been 5 years since I touched MFC... does it belong on the resume anymore?

I say, let 'em keep applying and interviewing... sure it's a pain on the interviewers, but they make me look like a programming superhero (and tbh, I'm only ok/good). The question is: someone please show me their resumes because I've gotta start putting whatever they've got on theirs, onto mine if they can get an interview and I can't. Hell, these days, I don't bother applying to most jobs because they ask for '5+ years exp in all of java/jsp/c#/asp.net/c++/winforms/wpf/mfc/sql/sql server/mysql/oracle' (literally, I'm not kidding). I think the point that should be made is: If you ask for ridiculous skills/knowledge then you're going to get ridiculous applicants.