3 ms·

> You’ve probably heard the following statistic: Men apply for a job when they meet only 60% of the qualifications, but women apply only if they meet 100% of th

> You’ve probably heard the following statistic: Men apply for a job when they meet only 60% of the qualifications, but women apply only if they meet 100% of them. Ah, I had not. Landing a job I don't know how to do 2/5ths of sounds awful.

liopleurodon 10y ago
depending on who's writing up the "qualifications" though, a lot of them are probably bullshit
- cholantesh 10y ago
  "10+ years of experience writing production systems in Elm" was a nice gem I saw recently.
  - deleted 10y ago
    [deleted]
- Namrog84 10y ago
  I am a fan of 10 years experience required in X. When X has only been around for 4 years.
- draw_down 10y ago
  Well, now you've got two problems.
khedoros1 10y ago
If it's just a programming language thing, those are easy to ramp up on, within weeks or months. Every job that I've had so far has involved a lot of extra learning. Even in the cases that I already knew the development language, there's been a large preexisting codebase, essentially providing its own in-house-built framework. The next position that I'm waiting for a written job offer for: I don't know the language, haven't ever developed on the OS, and I'll be looking at 15 years of legacy code. It sounds like an exciting opportunity to expand my knowledge on someone else's time and do something I haven't done before. Granted, I never would've applied on my own; they contacted me through LinkedIn. But that kind of thing is how I expect I'll find all my work in the foreseeable future.
dbcurtis 10y ago
> Landing a job I don't know how to do 2/5ths of sounds awful. Then don't be an engineer? Seriously, an engineer's job is to invent new things that no one has done before, and tell other people how to reliably build more of them. If you start a project with a 100% clear vision of how to get to the end, then you are already behind your competition. Not knowing how to do 40%, and not being intimidated by 95%, seems like about the right mix.
logfromblammo 10y ago
I have held enough different jobs to know that for some types of job posting, the listed requirements have almost nothing to do with the actual job duties and everything to do with imposing an arbitrary cutoff on the number of applicants to screen for it. Job advertisement: Immediate requirement for an illusionist/escapist. Must have 15 years experience in inverted underwater lockpicking. Nice to have some experience in juggling chainsaws. Job reality: You do coin and card tricks at children's birthday parties. Even if the job does require something you don't know, it is very likely that--no matter what it is--you could spend a few hours on the Internet learning how to fake it well enough to fool anyone short of an actual expert until you get the real on-the-job experience.

liopleurodon 10y ago

depending on who's writing up the "qualifications" though, a lot of them are probably bullshit

cholantesh 10y ago
"10+ years of experience writing production systems in Elm" was a nice gem I saw recently.
- deleted 10y ago
  [deleted]
Namrog84 10y ago
I am a fan of 10 years experience required in X. When X has only been around for 4 years.
draw_down 10y ago
Well, now you've got two problems.

khedoros1 10y ago

If it's just a programming language thing, those are easy to ramp up on, within weeks or months. Every job that I've had so far has involved a lot of extra learning. Even in the cases that I already knew the development language, there's been a large preexisting codebase, essentially providing its own in-house-built framework. The next position that I'm waiting for a written job offer for: I don't know the language, haven't ever developed on the OS, and I'll be looking at 15 years of legacy code. It sounds like an exciting opportunity to expand my knowledge on someone else's time and do something I haven't done before. Granted, I never would've applied on my own; they contacted me through LinkedIn. But that kind of thing is how I expect I'll find all my work in the foreseeable future.

dbcurtis 10y ago

> Landing a job I don't know how to do 2/5ths of sounds awful. Then don't be an engineer? Seriously, an engineer's job is to invent new things that no one has done before, and tell other people how to reliably build more of them. If you start a project with a 100% clear vision of how to get to the end, then you are already behind your competition. Not knowing how to do 40%, and not being intimidated by 95%, seems like about the right mix.

logfromblammo 10y ago

I have held enough different jobs to know that for some types of job posting, the listed requirements have almost nothing to do with the actual job duties and everything to do with imposing an arbitrary cutoff on the number of applicants to screen for it. Job advertisement: Immediate requirement for an illusionist/escapist. Must have 15 years experience in inverted underwater lockpicking. Nice to have some experience in juggling chainsaws. Job reality: You do coin and card tricks at children's birthday parties. Even if the job does require something you don't know, it is very likely that--no matter what it is--you could spend a few hours on the Internet learning how to fake it well enough to fool anyone short of an actual expert until you get the real on-the-job experience.