A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
Looking for support?
Looking for a community?
~Icon~ ~by~ ~@Double_[email protected]~
I'd say it's not okay to lie, but embellishment is encouraged.
For example, I hire programmers. If you put on your resume you know some language or framework, I'm probably going to test you on it. If you can't code hello world, or something basic I'm going to pissed off.
Now, if your role was technically something like a jr java engineer but you put on there that you were a mid level, meh I'm not going to check. As long as your skills are roughly in line I'll let you through to the next round.
Yes, I hire programmers. I need core competencies in areas I care about. If the job is Java but you've mostly been working in C# I'll take it on faith that you can figure that part out yourself.
If you tell me you've worked on ecommerce sites but can't tell me the steps of a credit card transaction, I'm concerned.
What I really care about is your ability to articulate your answers, clearly enumerate assumptions underlying your reasoning, and so on. If I have to pull teeth to get answers, I'm not hiring you. I'm an introvert, I used to love being left alone to write code in a dingy basement office, so I get that attitude but you need to be able to talk to people to get a job.
Part of that interaction is proving you have an understanding of the tools you will be using. If you lied about that knowledge and understanding, it will be painfully obvious very quickly.
I interviewed a guy who claimed on his resume that he ported a Blizzard game from PC to mobile. The way it was worded heavily implied that he worked for a company that was contracted by Blizzard to port the game, or at least that this was an official project in some sense, like maybe he worked with a group on the internet to do as a passion project, like how people reverse engineer and make open source versions of games.
Not only was it a school thing, it wasn't even like a project that he did. It was an example that his teacher went over in class.
He didn't know a single thing that was on his own resume. But he got the job anyway, even though we never did a technical interview for him. Guess whose daughter was his girlfriend? Yup, the VP of software.
Yeah that's a better way to put it to me. I honestly don't care what language most people code in, but I hope you can explain how you're doing stuff. I interview with the expectation of "a lot of red squigglies" expecting it not to compile. I don't care if you call .Sort instead of writing your own. Just show me you can code.
Sadly though, my latest question is for web developers and is mostly made up of calling a simple GET api. I have failed at least 80% of the engineers that take that test simply because they have no idea how to call an API in any language or framework, something I do I'd say on a daily basis. It's basically "call a fake endpoint /foo and show the results" and that takes mid level engineers the entire hour to do.
We just overhauled a programming test we use of we aren't certain a person can do what they say they can do (which is most of the time when you hire remote) and yeah the old one disqualified tons of people. It was very simple. I have had lots of people have someone else do it and then act very surprised when I wanted to discuss it with them.
Exact same problems, especially remote. I honestly don't know what is happening with engineers coming out of school/bootcamps, they just legit cannot code but go for these coding jobs. who is hiring them? I remember making fun of "fizzbuzz" as an interview question because it's too easy but I legit have had people fail fizzbuzz! In languages they chose!
I hate technical interviews, I've been given questions like "implement binary search", like okay, I can do that, but this is an annoying question. So I try to keep mine very light, "let's just chat about code, show me you can do basic stuff", and I'm just constantly disappointed.
It's rough out there and when you finally find them you they use your offer to get more money from their current job or another offer. Sigh. :)
People are taking an hour for
import requests
res = requests.get("https://your-domain.com/foo")
print(res.json())
or javascript's fetch that I don't want to type on my phone any more code for? Maybe I should think higher of my skills.
I’m not sure if this is embellishment or not but I wrote some sales software for a moving company. Then they used it for 15 years, and my resume now says I wrote software that brought in like $30m to the company.
I'd call it a legit claim. I assume as well that over those 15 years you've had to debug it and update it along the way. So that's completely fair to put on your resume.
Do not lie on your resume. Especially if you are a software engineer! When I give interviews, I typically don’t ask random technical questions. They are catered to what’s on your resume and if you can’t explain it, that’s a huge red flag
I think OP may need to explain further. There's embellishing your work history, or tailoring it to a particular position you're after. That's fine and part of the CV-fu. Then there's outright lying about hard facts, which can be a huge problem if checked.
Hard facts are things like who you worked for and when and on what position, or where you got your degree and what it says on it. Provable skills and certifications also fall under this category.
I wanted to hire a guy and then we found a lie on his resume. He said he had graduated but in fact he had a few weeks left to graduate. He would have the degree by the time he started the position. Our agency wouldn't touch him after that. A lie on the resume was a deal killer.
If he said "Degree expected on " rather than I have a degree he would have the job now.
If he could prove he was graduating in a matter of weeks then that's fucking ridiculous. I was accepted to grad schools before I even passed my final undergrad classes. It's just on a conditional basis, but nothing changed when I actually got the degree. Besides, there's time between the last classes ending and commencement, then months between commencement and getting the actual degree in the mail and your transcripts being updated.
I'm hope he feels like he dodged a bullet.
Did you lie and say you had already passed?
Probably not. HR would have just pre filtered him anyway.
I don't think it requires lying. I do think you can advance yourself faster by doing some lying, but you should stick to things that aren't actually job related. Length of time working jobs, increasing your previous job titles by a level, making your roles sound more critical are all good ones. Saying you can do something that you cannot can definitely get you in to trouble if they decide to ask you about it, or worse, you get hired and then they need you to apply the skill you don't actually have.
That being said, I have seen people straight up lie about their qualifications, get the job, flounder for a while and then become at least minimally capable and then hold the job long term. If you consider trying this, at least have a fall back plan for if you get fired.
I've got a funny story about that last paragraph!
A man I know who's retired now worked as a teacher for years in the 80s/early 90s because the secretary had to look in the phonebook for the phone number of the person that actually applied for the job. She tried the first person with the same name and he just went with it. He winged it during the interview, got the job and his sister who was a teacher taught him how to do it 😂
At some point, the question becomes: was the candidate too unqualified to understand what they were applying for?
I don't mind training someone if they're not 100% up to speed but they also need to be capable of learning and retaining things. A lot of that means that you need a foundation based on education and on the job learning. In other words, I'm not going to teach foundational shit that you should have picked up in high school.
One memorable example: we had one applicant who claimed a high degree of competence and related experience - and although I had some doubts during the interview I was realistic about the job market and our chances of finding someone who was a perfect match. She was personable, seemed smart, and had worked in the industry. How hard would it be to train her? If she could manage to pick up even the most basic parts of the workload it would be win to hire her.
A short list of what we learned
I'm going to gloss over a lot of irrelevant (but horrifying) detail here. We did have one memorable conversation where she said, "I'm so glad I applied for this job even though I wasn't qualified. You never know where you can get by trying!"
Where she eventually got was fired, but that took some time and the damage she did is still legendary. Part of that legacy of raging incompetence is that we fact-check resumes in ways that we previously did not. But the great irony is that she probably had no idea of just how unqualified she actually was. Again, the question becomes: is the candidate too unqualified to understand what they were applying for?
It really doesnt. Youre welcome to submit your resume into a place even if you dont meet all the qualifications(in fact, I'd recommend it) but lying comes off bad pretty much anywhere. If you cant show that your resume even kind of reflects your skillset any potential employer is gonna write you off
Totally depends on the employer. Some are hardcore, many aren't. I used to be in the IT field, one of the companies I worked for hired a guy who claimed he had 10 years of IT experience. He got fired after 3 days because apparently he couldn't even install a printer on people's computers.
If he was able to get past the interview, then anybody can lol. Better not to outright lie, but embellish for sure, just be ready to try to sound like you know the basics at least. Often, calling things fancy names is enough to get by, here's some examples:
Seems stupid, but trust me, it works with HR all the time. And once you get into the interview, you can add details to flesh out your experience better. A lot of it is how you say something, not what you say.
Don't say, "I set up a Minecraft server once for my friends to play." Say something like, "I spun up a Minecraft server instance for my friends and I to utilize. I managed scheduled software updates and patches for the server, verified the disk health and hardware usage, and set up regular backups for the world files and resources." Doesn't matter that your hardware monitoring was just Windows Task Manager and your scheduled backups and updates were just Windows Restore point and Microsoft updates, most staff will just hear that description and move on, especially if you add a little banter, they will normally just go, "ah cool" and keep going down the list.
Obviously this varies based on the job experience level, but for entry level jobs to get your foot in the door, it works very well.
I have an interview coming up. Can I get you to dress up as me and go to the interview?
The current system of job seeking often requires to lie on resume.
This has not been my experience at all, but maybe it depends on what kinds of jobs you’re seeking.
In my line of work, detecting lies on resumes is one of the reasons we spend time interviewing candidates. If you are caught out in a lie, you can kiss any chance of an offer goodbye. As an interviewer I have never knowingly given a “hire” vote to a lying candidate and if I did, I wouldn’t have my job much longer.
Why is it you think that job seeking often requires lying on your resume?
I assume it's because they don't have a very good resume and won't get called/interviewed otherwise.
Lying only paints you into a corner. It also means you’ll probably get saddled with work that doesn’t suit you.
Jesus, all the people here saying never to lie on your resume must live pretty privileged lives.
Yes, its okay to lie, if you can back it up.
For example, I know just about everything there is about computers/sysadmin there is under the sun (im a born computer geek) but I never had any official degrees for it. I lied and said I had most of the CompTIA certifications and not a single person ever asked to actually see it. I already know everything that's in those books so it's not like I didn't have the knowledge, I just didn't have the stupid piece of paper, that, again, no one ever asked for.
Most employers are going to be exploiting your labor anyways so if you can take advantage of them you should, because they certainly going to be taken advantage of you, and you shouldn't feel bad for them.
As others have said, just keep it reasonable and don't lie yourself into a corner. If you don't know rocket science don't say you do and obvious things like that.
Remember: It's not just a fact of, what's going to get me the result in this particular interaction. It's a question of, what type of person do you want to be?
Lying on your resume, within reason, is probably a good strategy for getting the job. It's not a good strategy for life.
it really depends on what
padding the years of experience for a specific skill from 4 to 7.. not really a big deal in my opinion. someone's 4 years could be more valuable than another's 7
if you're making up whole degrees or careers.. then it becomes impractical because you'll have to walk the walk. if you're frank abagnale, maybe you can do it. for us regular folk it'd be hard to convince someone who knows what they're doing that you know what you're doing when you actually don't
If one person’s 4 years can be more valuable than another person’s 7, then considering the number of years is a waste of time anyway.
Like if you’re applying to a company with a hard limit of minimum 5 years’ experience, and you have 4 that you think qualifies you, and the company isnt willing to consider you because of it, that’s not a company you want to work for.
They know, that’s why there’s verification of stuff that’s critical to them. Most company don’t care if u know ur job
I've only ever even had one job call anyone I had on my resume.
I know this, because every contact info other than my own on my resume for the last 15 years has been fake and will forward to my own phone so I can pretend to be my own reference if I need to.
I could probably lie about being able to actually do the job and having past experience in it, too; but that would be a little silly since I wouldn't be able to actually do the job and they would find that out pretty quick.
Do you use any kind of voice masking for this?
Nope. I just saw the forwarded number and act. Remember now, I've only ever actually had one place actually call. And they called everything.
I did also get the job.
I'm just imagining you thinking up different characters for each job, Daniel from the supermarket, he's young, into fitness, goes to the gym daily, so you're putting on a tough muscle man voice, then it's Sheila from the library, quiet mousy lady, 65, maybe Scottish? Now you're doing a Mrs Doubtfire voice.
This would be a fun scene to watch. I'd check out that movie/TV show.
I've never been coached to lie on my resume.
I've never put anything false on my resume.
I'm glad to have not worked for a company where that's cool, or knowingly worked with scumbags who lie about their qualifications.
Sure, my resume sucks, but it's at least accurate.
Why do you think it requires you to lie? If you're lying on your resume it's (I can only assume) you are not actually qualified for the position you are applying for. I also assume that you are at more of an entry level in terms of your skills/qualifications. Is that accurate?
If you have success with that strategy good for you, but I'll caution others - as you get further in your career, interviews get longer and more in depth. If you say you know how to do something, you are often asked technical questions on that thing, or in-depth questions on how you'd implement that thing/skill/strategy/into the position. As others have said lying and embellishing are not the same thing. You can oversell your skill to a degree, but be prepared to need to put in extra work (probably off the clock and in your own time) to get yourself to the skill level you said you had. You may not need to! But in some positions, you may be RELIED on for that skill you're not as good at as you said you were.
Also - UPDATE your resume and keep it current. If you learned a new thing and can do it, put it on there before you forget you did it. Also, prioritize. Remove old things from your resume as you get further into your career and those skills/accomplishments are less impactful or Relevant. Replace with newer things. Keep track of what's going on in your field and stay up to date with buzz words and topics and be able to speak to them even if it's not your area of expertise.
Because you are at a disadvantage against those that do? I guess it depends on how definition of "required" and I feel like the context dictates the definition of "required" to be "required to be competitive."
Job listings often list unrealistic or impossible qualifications (such as 10 years experience in a programming language that's only existed for 6 years, most famously), overblown or unrealistically wide scope (must be expert in Linux, Windows, Cobol, C++, Atari, and to do the Kessel Run in under 12 parsecs), etc...
So to actually get a job you may be perfectly qualified for, it's requires lying. The trick is knowing what's bullshit on the job listing and what's important, and if you are qualified for a particular position, you should know what parts are bullshit. Lying in that instance seems fine to me.
Companies lie on their job ads so I think its perfectly fair. I wouldn't go and say I can do a skill that I can't but I don't think it's wrong to say I can do x even though i have no qualifications or professional experience in it.
Depends on the place, but most don't seem to care if you embellish your credentials as long as you're able to do the job. A lot of job postings overstate what the job requires anyway.
If they ask for 10 years experience in a technology only released 5 years ago you could claim spending the last 40 years of your free time on the analysis of early 21st century literature if you are only 30 years old but they would probably be upset that you pointed out their stupidity.
My place fired some guy when they found out he didn’t attend the college he claimed to have a degree from. Not sure why it took almost a month post-hire to figure it out, and wasn’t discovered during the initial background check.
Depends on the place.