9 ms·
Maybe try interviewing a few people who you think "aren't worth interviewing." It could be that your standards are unreasonably high and you're dismissing plent
by fiblye 7y ago
Maybe try interviewing a few people who you think "aren't worth interviewing." It could be that your standards are unreasonably high and you're dismissing plenty of capable people.
And lets be honest, looking at most job postings, most people have absolute ridiculous expectations of candidates. Most things you can and should be able to train to some extent on the job.
- mattmar96 7y agoFair point. "Aren't worth interviewing" may have been a little harsh. I can assure you, there are no "harsh requirements" on our listing. That would be the case if we had too many applicants! It seems we need to use a recruiter or something, everyone here seems to think its ridiculous that we can't find people.
- astura 7y agoCan you share your job listing(s)?
- robertfw 7y agoI just saw a job posting that was looking for someone with 3+ years of experience, and the list of required skills would have taken easily double that working flat out to acquire
- rumanator 7y ago> and the list of required skills would have taken easily double that working flat out to acquire You're reading too much into those requirements. Nice-to-haves are not must-haves. I've been involved in hiring processes for a front-end position that listed non-trivial experience with React and among the half dozen candidates who applied the company even considered a high-schools dropout who only had to show a 50-hour HTML online course.
- maxmalysh 7y agoI remember a job posting asking for 5+ years of Android experience in 2013 (Android 1.0 was released in late 2008).