As a former recruiter, I just assume all resumes are complete shit. I never saw much of a correlation between a quality resume and a quality candidate. Screening for the stuff one uses on the job is what I prefer to do. It's also nice to focus on the job requirements, too, because it removes any need for someone to impress me with what the have done. When you can walk into an interview with "hey, I really want you to get this job, but we need to find a way for both of us to envision a scenario in which we're working together successfully", it's amazing how well that usually turns out.

If recruiting software didn't penalize for keywords I think it would be less of an issue. Its a struggle trying to figure out what to put in the "list of technologies" type section. I have to put them somewhere to get past crappy HR screening software since explaining every tech in a job description would create paragraphs but just listing it doesn't represent the level of aptitude.

For example, I might use Chef daily. If I put it in a list of other tools I use it can mean I know how to use it for my very specific use case, but usually it is taken as "this guy thinks he contributes to the Chef source code and knows every bizarre scenario involving it" by some tech screener trying to get his rocks off.

I 100% blame every tech recruiter for furthering this mess.

I’ll go even further. Don’t put any language, framework, technology on your resume that you don’t want to talk about or that you don’t want to do.

I took C and C++ off of my resume years ago even though I did both for 12 years and I still know all of the ends and outs of C. There is going to be that one old geek (I’m 45) who wants to ask me some obscure question just to prove how smart he is. I definitely leave PHP and Perl off. I don’t want to show up on recruiters search results looking for WordPress developers (I never did WP).

I want to keep the conversation and the interview focused.

>>> class vs interface

This is java specific, that's not OOP.