this post was submitted on 28 Oct 2024
331 points (98.0% liked)
Showerthoughts
29692 readers
1496 users here now
A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. A showerthought should offer a unique perspective on an ordinary part of life.
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- Avoid politics
- NEW RULE as of 5 Nov 2024, trying it out
- Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct-----
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have been working in tech since ~1995. I also have been in a hiring position since 2002 and own the top firm in our field. Here is my advice; lie.
Let me clarify. A lie is only problematic if by the time you start in that new position, you do not have the skills to back it up. If you can do the job and do it well, no manager will ever give a fuck about what you put in your resume.
PS: In most cases, the school you graduated from will only matter for your first job. In most cases, your GPA will never matter.
I've been working in tech since 2000 and have been in a hiring position since ~2008. I've done very well for myself, and continue to do well, and I've never had to lie. I've always just treated most of the down page requirements as "nice to have" or "have something similar" rather than hard requirements, and have always been upfront about it in interviews about the actual amount of experience I've had in these things. What kind of interviews are you running where you aren't asking about the requirements for the job? One of my main goals in interviews is to discuss what the candidate has worked on so I know how well it fits into what we're doing.
I do agree that if you do the job well, no one is going to ask questions. But if looks like you've lied to get the job, it makes it pretty easy decision to fire you if things are going poorly.
I think you're missing the main context of the post, which is experience. It doesn't matter if you were not an expert when you applied. What matters is that you are an expert when it is time to be, which includes the interview.
That said, common sense tells you that this is all about "additional skills" like specific softwares, not core technologies. If you've never heard about Java and you apply for a Senior Java Engineer position, you're probably not going to do well.
Again, I'm curious as to what kind of interviews you are running if you aren't catching people who claim to have experience in something, but have only basically crammed online for (at best) a few weeks between an interview request and actual interview. I feel like if someone had tried to become an expert in the field during such a short time, it would be painfully obvious, unless they were an Olympic level bullshitter. Also, if you claim to have experience in something, and I ask about that experience, and you make it up, that is still lying.