4 ms·
I can sit there and spend significant time per application elegantly explaining how the details I've already put in my resume are relevant to the job descriptio
by transcriptase 3y ago
I can sit there and spend significant time per application elegantly explaining how the details I've already put in my resume are relevant to the job description, only to have it never reach a human because a poorly designed parser didn't find a keyword or ML gave it 1 point under a set score threshold.
Or a human could just read the resume.
- linsomniac 3y agoI'm slogging through resumes now and thought back to your reply above... Here's the thing: If you're willing to accept that your resume will be passed over in preference for people who wrote a cover letter, that's fine, but a curious position to be in if you are looking for a job...
- linsomniac 3y agoThis is a Mexican standoff. You aren't willing to write a cover letter, because a machine might be reading it, and we are getting resumes that, on their own, are just a "maybe" along with 100+ other "maybes". On the other side, we have been inundated with "fire and forget" resumes that make it hard: why should we invest time in your resume when you haven't invested time in your application? In our case, we have 3 out of 10 people at the company reviewing these resumes (CTO, senior sysadmin, full-stack dev). We are committing significant resources to reviewing applications. If you are going to optimize for submitting to a machine that scores your application, don't be surprised that a human isn't reading your application.
- nprateem 3y agoChuck them through AI and ask how suitable the person is.