Earlier quoted context omitted.
I love the "looking for experts in X" followed by "with one to two years experience". And then I see my neighbor who is an expert in X, can code rings around anybody, but can't find a job after his company shut down. His only fault is he's 60.
At 60 you just got a few more years to work until you have to retire. It takes 2-3 years to really get comfortable with some bigger code base... So if you are looking for some longterm employee (if such a thing even exists), it's not worth it.
You Only Need 50% of Job “Requirements”
71–80 of 254 posts
Re: You Only Need 50% of Job “Requirements”
#72Earlier quoted context omitted.
>The position had been open for almost a year. I think there's a reason. Fake job openings to keep HR people busy?
Or more likely fake postings to show investors they are a successful company that is hiring.
Re: You Only Need 50% of Job “Requirements”
#73But I'm not sure that the sales pitch this article is trying to make is valid. They claim at the end that they'll get you 5.8x more interviews. But is that good? In my 3 interview processes, they each brought to light reasons why it was not a match in one or both directions. The article even touched on that, as candidates will self-screen out of jobs that aren't quite right. It would have been a huge waste of time to expand that to 10-12 interview processes that were not matches. Especially when I didn't end up taking a job even from the ones that went well, and re-joined an old team instead.
The screening that happens in the hiring process can feel frustrating when you really need a job, but I appreciate being screened out when it would not have worked anyway. It saves everyone time, and hopefully puts me in a healthy long-term role that will last for years.
Re: You Only Need 50% of Job “Requirements”
#74Re: You Only Need 50% of Job “Requirements”
#75Earlier quoted context omitted.
At 60 you just got a few more years to work until you have to retire. It takes 2-3 years to really get comfortable with some bigger code base... So if you are looking for some longterm employee (if such a thing even exists), it's not worth it.
I disagree, unless you and I have radically different definitions of what "comfortable" means. If I'm hiring an engineer with the seniority I'd expect them to have at 20, 30 or 40 years in industry then I want them to ramp up inside of a year. I'm not going to expect them to be completely self-sufficient within a month. But they should be capable of implementing performant solutions to nontrivial problems with autono…
For me personally the worst unsecurity is not knowing where to put new code, without messing up some architectural separation that I'm not aware of.
Re: You Only Need 50% of Job “Requirements”
#76I've only once ticked of roughly 95% of job requirements. I didn't get the job. They actually cited the 1/20 requirements I didn't fulfill and said they can't hire anybody who doesn't have that. They wanted a 100% candidate. Looking through the list of the things they listed as must haves and that they wanted an internal candidate I showed them it is statistically very unlikely they would even find a better candidate…
Seems to me that this was a job put together with a specific person in mind and somehow that didn't work out and they just didn't know what to do after that. Seen this same scenario play out before at multiple companies.
Re: You Only Need 50% of Job “Requirements”
#77You can eliminate all kinds of selective bias and incompetence by first filtering candidates based upon a battery of personality tests. You don't have to know anything about the candidates until this pass through the initial filter.
Aside from personal experience, can you point to any data on this, and maybe go into some more detail? When I think of personality tests, I think of quack science. "Do you get angry a lot?", "Is it easy for you to get angry?", "Would you say it is difficult to make you angry?, and four other similar questions in a 200 question quiz. They ask the same thing multiple ways to try to know if you are an person categorizab…
Also, anger is an emotion opposed to a personality designation.
Re: You Only Need 50% of Job “Requirements”
#78A recruiter once told me "we ask for God in person, hoping for a prophet, we are happy when we get the followers".
That's a good way to get the worse part of developers divided by their Dunnin-Kruger score.
I worry that the questions that I only ask questions of candidates that I think are important and that I already know the answer too.
If you're looking for good hires you're going to want people who know stuff you don't and finding that out is tricky because of the Dunning-Kruger effect.
Re: You Only Need 50% of Job “Requirements”
#79Earlier quoted context omitted.
I read that a different way. I understood it as an ad from Company X which lists '5 years of Python' as the requirement. Candidate 1 has 5 years of Python at Google, and Candidate 2 has 5 years Python at InfoSys.
Does the Google experience really teach one that much better? Or is it just perception? I mean, at the end you are just a little cogwheel in some big corporation anyway. The python tasks you need to solve there are probably just as mundane as everywhere else.
Startup founders looking for VC money want to be able to add "Team of ex-Google, ..." to their pitch.
Re: You Only Need 50% of Job “Requirements”
#80You can eliminate all kinds of selective bias and incompetence by first filtering candidates based upon a battery of personality tests. You don't have to know anything about the candidates until this pass through the initial filter.
This sounds like the old joke "avoid employing unlucky people by throwing away half the CVs you receive". What is the optimum personality type to employ for a specific role anyway? You might hire based the idea that you want people who won't "rock the boat" and just end up with a group that are shy of giving you bad news.