Abstract: Don’t lie on your resume. Ever. If we don’t immediately shine light on damaging advice, then we secede our integrity to the misinformed.
A question was asked recently in the “SOFTWARE-TESTING” Yahoo group from someone who was seeking advice on how to better construct their CV/resume. A lot of tips starting pouring in from the group, and all seemed relatively innocuous until one specific recommendation was posted. The recommendation pointed to an article that suggested there were appropriate times to lie on your resume, or as the post put it “exaggerate” certain elements.
Here’s a quote from the post that was referenced:
“What should you do in case you have only 2+ years of AngularJS experience and want to apply for this job [requires 3yrs]? Realistically speaking you are the most experienced developer who is willing to work in Montreal with AngularJS. You should exaggerate your Angular experience and put 3 years on a resume. Otherwise there is a risk that your resume may be discarded as not meeting minimal requirement. Could you imagine all developers being honest and this agent getting no response to such job post? Nobody would benefit from such honesty. To make this agent and his client happy you need to lie on your resume. – [Author’s name removed]”
Now, usually I credit my sources, but in this case, I will not link to the original article or post the author’s last name, as I believe people can change. If this person were ever to have a change of heart and take down the detrimental post in hopes for redemption among the community, then I would not want this post to stifle that. I did send a strongly worded reply, stated below:
“[Author’s name removed], I do not know your context, but I would steer anyone away from this logic. It is unethical, in my opinion and simply not necessary given the risks. I would strongly suggest NOT doing this. When should you lie on your resume? Never. If a company uses years of experience as a sole deciding factor for eliminating my resume, then I wouldn’t want to work there, so thank you for not wasting my time. I believe a good heuristic is simply to tell the truth 100% of the time. Putting “3 yrs” on a resume for someone that has “2 yrs” of experience is just asking for trouble. It can easily be challenged and then your professional reputation is at stake. Your name becomes tarnished in the industry as a liar. We are not in the business of misleading others, quite the opposite. This is not for me, but that’s just my two cents. – Connor”
But you don’t need to take my word for it, check this out.
So, did my reply make an impact or simply bounce off? I’m not sure. Would I love to see that person take their article down for the sake of the community? Yes. On the other hand, do also I realize that people have to come to realizations on their own, sometimes learning though experience before they will gain a visceral understanding on some topics? Yes. As soon as I saw this recommendation, I knew a reply from me was going to happen, it was simply a matter of time. This comes from a feeling of responsibility, that the onus is on us to call these things out when we see them appear in the testing or in the larger software communities. If we don’t immediately shine light on damaging advice, then we secede our integrity to the misinformed.