You are viewing a single thread.
View all comments View context
1 point
*

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.

permalink
report
parent
reply
2 points

Thank you for your valuable insight.

permalink
report
parent
reply

Microblog Memes

!microblogmemes@lemmy.world

Create post

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:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

Community stats

  • 13K

    Monthly active users

  • 1.5K

    Posts

  • 46K

    Comments