First, if you’re not comfortable doing the work, don’t add it to the resume. Ultimately you are curating your career and your resume, and fake experience, need to reflect that trajectory.
Second, HR is not allowed to add random garbage to the req. In my companies, that would get you fired on the spot. If you come across a company that does that, then you came across a company to avoid. What’s listed in the req is what the manager thinks they’ll need, which doesn’t mean it’ll always be correct. The req should also list the requirements in descending order of importance. A inexperienced manager might not do that at first, but after being flooded with resumes that prioritize skills that weren’t actually that important, they start to adjust the job listing.
The point about skills listed in order of importance is one I’ll surely have in mind from now on, thank you. But if it is not stated anywhere it might be a wrong assumption as you pointed out.
Ok, I was a bit vague, what I meant is rather that HR will list everything from “absolutely necessary” to “an interesting skill if you have it” under the requirements. The nice to have part is good, but do not always get treated the way it should.
I really would not like to fake experience in order to get somewhere to work on something. Sometimes there are positions that clearly differentiate what job needs to be done and what you need to know, those are not always the same things. So to summarize I rant about things being opaque more than things being messy, this really complicates things, especially when you get used to a specific culture and then move to another one.
Your main job is to further your career. If you’re interested in a skill your choices are to convince your employer to engage in a project that requires that skill or train yourself and lie about your experience. My experience is in tech but both my wife and I started in finance. It was very clear that with our degrees we would achieve nothing so I put my PC skills and my piracy know how to work. I built our first home lab then and we’ve had one ever since. Even to this day we spin up proof of concept environments to “hands-on” and learn how certain products behave and interact. The point is that none of that shows well on a resume but your ability to speak on the subject does show during an interview. The resume is there just to get you to the interview, nothing more. If you have the know-how but not the corporate experience, lie.
PS: Your employer will only give you a limited set of use cases for your skills or desired skills. You should always expand that on your own. It’ll make you more marketable than the competition.
First, if you’re not comfortable doing the work, don’t add it to the resume. Ultimately you are curating your career and your resume, and fake experience, need to reflect that trajectory.
Second, HR is not allowed to add random garbage to the req. In my companies, that would get you fired on the spot. If you come across a company that does that, then you came across a company to avoid. What’s listed in the req is what the manager thinks they’ll need, which doesn’t mean it’ll always be correct. The req should also list the requirements in descending order of importance. A inexperienced manager might not do that at first, but after being flooded with resumes that prioritize skills that weren’t actually that important, they start to adjust the job listing.
The point about skills listed in order of importance is one I’ll surely have in mind from now on, thank you. But if it is not stated anywhere it might be a wrong assumption as you pointed out.
Ok, I was a bit vague, what I meant is rather that HR will list everything from “absolutely necessary” to “an interesting skill if you have it” under the requirements. The nice to have part is good, but do not always get treated the way it should.
I really would not like to fake experience in order to get somewhere to work on something. Sometimes there are positions that clearly differentiate what job needs to be done and what you need to know, those are not always the same things. So to summarize I rant about things being opaque more than things being messy, this really complicates things, especially when you get used to a specific culture and then move to another one.
Your main job is to further your career. If you’re interested in a skill your choices are to convince your employer to engage in a project that requires that skill or train yourself and lie about your experience. My experience is in tech but both my wife and I started in finance. It was very clear that with our degrees we would achieve nothing so I put my PC skills and my piracy know how to work. I built our first home lab then and we’ve had one ever since. Even to this day we spin up proof of concept environments to “hands-on” and learn how certain products behave and interact. The point is that none of that shows well on a resume but your ability to speak on the subject does show during an interview. The resume is there just to get you to the interview, nothing more. If you have the know-how but not the corporate experience, lie.
PS: Your employer will only give you a limited set of use cases for your skills or desired skills. You should always expand that on your own. It’ll make you more marketable than the competition.
Yeah, the “lie about what you did, but only if have that experience firsthand” sounds much better strategy to follow, thanks for the explanation