2 ms·
I don't have nearly as much experience as you, but I've been doing the same thing. After giving a ton of interviews to people who put "concurrency" or "multith
by tombert 8y ago
I don't have nearly as much experience as you, but I've been doing the same thing. After giving a ton of interviews to people who put "concurrency" or "multithreading" as a skill on their resume (yes, really), I realized it's better to keep the information clear and relevant; listing off a million languages or vague skills is an easy way to make an interviewer look for reasons to call bullshit.
The recruiters I've dealt with usually want to slap on a bunch of crap like "Web scala Java OOP web-scale MEAN STACK" onto the resume before they submit it, but the solution to that is to do it all in LaTeX so that they don't know how to work with it :)