3 ms·
so many quite good candidates won't apply. Shame on someone for writing unrealistic or unnecessary "requirements", but also shame on the engineer who doesn't e
by dfxm12 8y ago
so many quite good candidates won't apply.
Shame on someone for writing unrealistic or unnecessary "requirements", but also shame on the engineer who doesn't even apply because of them.
I wonder how truly good a candidate is if they get discouraged so easily. Maybe a hidden requirement 1 is showing a willingness to try to punch above one's weight or displaying some self confidence during the application process. After all, what's really the difference between 4 years of development experience in X language vs 5?
- pavon 8y agoI'll apply to a small company f I meet what seem like the most important of the requirementstc. . But it is a largedompany I assume that a large company filtered outjust by HR you don't meet 100% of the require. I've I used to but afterhaving never interview from ain those cases, 've stopped me.
- logfromblammo 8y agoI don't want to waste my own time on an activity I actively despise. I am perfectly willing to apply to a posting with missing requirements, right up until I have to create an account to apply, chop up my resume into pieces, and paste the bits into form boxes. That's when I say, "screw this, it wasn't a close match anyway". If the application process is "attach resume document to an email" then I might even spend some extra time on the cover email, explaining why am applying without being a 100% match for the requirements. The difference is the expectation of a payoff. That application management system is going to automatically filter out mismatches, and making me do all the work to disqualify myself as a candidate. The email might get read by an actual person with an interest in the outcome.
- linuxftw 8y agoToo many job requirements is a symptom of a bureaucratic hiring process, which is a symptom of a bureaucratic work environment. I've found cold-applying to these types of positions bares little fruit. On the flip side, I don't mind an overly ambitious position description if a recruiter has reached out to me. I know I have an actual human on the other end, and they have enough sense to determine I might actually be a good fit.
- potta_coffee 8y agoAnecdotal, I didn't meet most of the requirements for my current gig, but I applied because they listed one framework I'd been using quite a bit. I ended up being getting hired and pretty much being the senior guy there.
- pmiller2 8y agoI'm not sure if this is the best place to drop this anecdote, but I looked at a position where the responsibilities included working on the backend API and partner integrations, third party integrations, machine learning, internal tools and reporting, devops, and Postgres administration (including query optimization, horizontal partitioning, and reliability). Since it was a small-ish company, I thought maybe this was just their generic "senior software engineer" posting. Nope. I asked them. They actually expected people to be able to work on all of those things. By my count, that's about 5 different teams that should be working on those things... except that this place has ~15 engineers. I self selected out of that process because, although I could certainly do the API and integrations stuff, if I'm the best person you've got to work on ML, your company is in bad shape. I probably could have applied and gotten an interview anyway, maybe even gotten the job, but I know it wouldn't have been someplace I could do my best work. I'm very glad I'm not there.