For example, I once posted a job that included the word "Ruby". I thought the job posting made it clear that Ruby was a very, very small part of the job. But I still got several resumes from people who were Ruby experts or at least claimed to be, and that is all the experience they had given their resumes. They had little or no non-Ruby experience. At the time, I needed someone who could write Ruby code but had much more experience elsewhere.
So the resumes helped me screen out those candidates. And I also learned that my job posting was worded incorrectly.
It just means: don't select people for their getting-a-new-job skills. Those skills aren't relevant to software development work.
It would be helpful to know more about what you do versus what you don't.
Which is why I wrote that blog post. Just to make sure it stands less of a chance to get screened.
Phone screeners --- who barely count for anything in our process, but don't get me started on that --- might skim a resume just so they have something to start talking about.
Otherwise, our hiring process is resume-blind.
We bring people in directly out of school, from random line-of-business programming jobs all around the country, and from networking jobs for people who want to transfer into something more developer-y.
I should mention: our work is not easy. I can hold my own in an argument that says we're significantly more technical and significantly more sophisticated than the median Silicon Valley startup.
Resumes are worthless. Do not bother. If you're screening with resumes, you're doing something wrong.