...though I have had agents asking me to massage my cv so it will fit the requirement more closely. Won't do it - just can't see the point - I don't want to bluff my way into a role I can't do and won't enjoy and it won't last long and that will look bad on my CV. Also, don't stretch the dates as many City banks now use reference services that check your cv quite carefully and you will lose an opportunity if you lie.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum
I agree, why lie, you will get in the job and then you can not do the work then they will let you go. pretty simple. Be honest. not to mention you have to go and take an interview, what if they ask questions on something you said you know.
My Recent Article : CDC - Change Data Capture
Skill's are like our own assets.It will really fetch you alot.So don't lie about your skill's.Like if u know Jquery up to Some extent just say how much you know it?But never exaggerate about your skill's .
Our job is such that lying about our skills is fundamentally pointless, because a single question on the subject will clear things out. As for lying about projects done etc. - well, it depends on whether you value your reputation. For example, if you are into consulting, any sort of misrepresentation will kill your reputation and thus your business.
because a single question on the subject will clear things out.
Unfortunately, a single question can also give someone the wrong impression. When I was interviewing last year, one of the questions dealt with threading and semaphores. Now, for the majority of work that I do, I don't really have to think about threading, and if I do, I'm not worried about mutexes, semaphores, blocking, etc., unless there's some cross-thread communication required, which I try to avoid. And besides, when I know I need a mutex, I look up the various options and figure out which one I need. So this information is not in my head where I can just spew out the various options and nuances of each.
And ironically, just about every phone interview question I was asked had no applicability to the actual job. I hate interviews, especially phone interviews. If I ever have to interview again, I am going to refuse doing a phone interview, even if it means missing out on 90% of the "opportunities" out there.
For a new graduate from school, a little exaggeration is acceptable. He might be able to do a lot of things just by the experience accumulated through the assignments in programming courses, but he never worked on a "true" project.
Some of my friends, In their CV in Skills & Projects section, they put new version instead of actual version they have worked.
Example (VS 2010 instead of VS 2008, SQL Server 2008 instead of SQL Server 2005, C# 3.5 instead of C# 2.0)
True fact......But when they receive mails like "Need .NET Developer with 3.5 framework", they don't want miss that one (actually they worked in lower version). So they just replace the versions in CV. That's it.
In some interviews, HR asked about Linq, etc.,(which not exists in lower version), they can't able to answer that.
But after couple of interviews, finally some of them got a job
The sad thing is, you can't reply to such calls honestly. Most corporate legal departments would throw their hands up in horror if you spoke with a former employee's prospective employer. There have been far too many successful litigations based upon such statements.
"I can confirm that John Doe worked at My Company from Start Date to End Date. Beyond that I have no comment."
You've said exactly nothing critical that Mr Doe could make an issue of, but the fact that he wasn't able to find references who praised him to the sky will be immediately obvious to the HR drone calling you and allow him/her to draw the correct conclusion.