But anything on your resume or linked from your resume is fair game.
If you haven't been able to meaningfully participate in open-source work there's no penalty, but don't link to an empty GitHub page on your resume.
Nobody is a expert in everything, of course, but if you specifically put "TCP/IP" or "OOP" on your resume, you better be able to explain TCP vs UDP or class vs interface (both real examples from real phone screens I've done).
You could probably drop education from it if you have 5 or more yoe.
Frankly you could do this in one 5 or 6 line paragraph without a resume
I never read them anymore. It’s such a waste of time. Totally useless compared to our phone screen templates.
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.
When I am looking for a job, I send my resume to my curated list of local recruiters followed up by a phone call. We talk about what they have available and what I am looking for. I have enough of a history with them that they make sure that my resume shows up on top of the hiring managers stack.
My success rate from submitting my resume to being invited to an in person interview is 100% unless the req was closed. My non rejection rate is close to 100% (I’ve taken myself out of the running because I found a job.)
Mostly LinkedIn these days. I only got really serious about my career about 10 years ago. Before that I was your typical “dark matter developer” working at one job for almost a decade.
“Hey, I am not looking to make a move right now/I’m looking to make a move in $x months. What are the trends you are currently seeing and what are the salary ranges? Send me a list of open reqs. I might know some people who are looking”.
This will also let me stay up on market trends and know which projects to focus on and what to emphasize on my resume.
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.
This is java specific, that's not OOP.
C#: https://docs.microsoft.com/en-us/dotnet/csharp/language-refe... TypeScript: https://www.typescriptlang.org/docs/handbook/interfaces.html
Granted, it might be less prudent to skip some fields than others, of course.