this post was submitted on 15 Dec 2024
1682 points (98.1% liked)
Microblog Memes
6053 readers
3614 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean to be fair, it's a struggle between terms like "expert" or "senior" being too ambiguous and a time interval of experience being a poor indicator of actual proficiency. The corporate world doesn't care though and ties the two together as a general rule because middle management isn't smart enough to tell the difference. Thus, it boils down to "we're hiring a senior level, it takes X years to reach that at our company, thus we expect someone to have that many years of experience at any other company doing a job similar to what we do". Some HR peon then words it like "you need X years of experience using [exact technologies we expect applicant to use]".
To tie this back to the OP: Most (?) people understand this is what is happening in basically all job postings where they list years of required experience to match their expected proficiency (i.e. I'm as good as someone who has been doing this for X years), but there are people who interpret this literally and think that if they have X-0.1 years of experience in that exact thing that they will be automatically rejected because it said X is required and they do not have X.