3 ms·
Maybe this works in big companies, but many small companies that I’ve worked at, you’d be caught, even lying on silly little things. The people reading your
by kube-system 5y ago
Maybe this works in big companies, but many small companies that I’ve worked at, you’d be caught, even lying on silly little things. The people reading your resume are the same ones you’re going to be working beside, and they’ll absolutely ask you about things you said you knew.
And once they find out that you lied about your volunteering experience at your local little league team, your whole resume goes under the microscope. I’ve seen it happen.
- austincheney 5y agoThere is a couple of problems with that. More than half the time I have interviewed nobody reads resumes. They know your name and kind of how long you have been employed. Second, you control what appears on your resume. You can spin it how you want by the facts you include and omit. You list the great selling points about yourself and none of the bad. Don’t lie on a resume because its already under your control and it’s a document of record that can follow you from any point in the past. This tread isn’t about resumes. It’s about interviewing, specifically as a discussion.
- kube-system 5y agoWhen I interview, I don't spend much time reading the resume beforehand, but I'll ask a few specific questions about it during the interview. If one assumes nobody reads their resume, however, then what benefit would they get from lying?
- austincheney 5y agoA resume is not an interview.
- kube-system 5y agoI never said it was. It’s a reference that most interviewers will have on hand before/during the interview.
- b20000 5y agowhat is it with lying on resumes? is that a thing? i went through some interviews a while ago. everyone assumed i lied on my resume without any basis to do so.
- isbvhodnvemrwvn 5y agoVery frequent, sometimes it's straight up lying, more often it's overstating what they did on the CV. To give you an example, when recruiting for a devops positions recently, during phone screen easily 1 in 4 people with several years of AWS experience on their CV had no idea whatsoever about very basic IAM concepts (e.g. roles vs users, that explicit deny always takes precedence over explicit allow). That being said being civil and ensuring positive experience even for poor candidates is one of the fundamentals of interviewing. In the cases I described I didn't call them liars, I simply stated that for this role we expect them to independently support development teams, and that we consider IAM to be part of the fundamentals (it was explcitly listed in the job posting), and sent them some resources for studying up.