5 ms·

Woah, that is way more insidious than I was expecting. I get what you mean now, and that just seems really stupid on the recruiter's part. Doesn't it come out d

Woah, that is way more insidious than I was expecting. I get what you mean now, and that just seems really stupid on the recruiter's part. Doesn't it come out during the interview process if there's BS on the resume? But I'm guessing that's your point, right? Because the hiring manager should notice, and the interview process should screen for it, so this must be a symptom of much larger scale dysfunction in the tech recruiting/hiring space.

dsr_ 4y ago
In the best case scenario, the recruiter called up twenty prospects and said "Quick question -- have you worked with FOOLAND?" "You mean FOOlang? Yeah, a little." "And what jobs did you have when you did that?" "Uh, I learned a little about FOOlang in the job I had from 2010-2012, and then it came up again in the job in 2015." "Thanks! I think I'll have something for you tomorrow." And then the recruiter edits "Skills" to include six years of the still-misheard FOOLAND. Everything else is worse.
Aeolun 4y ago
> Doesn't it come out during the interview process if there's BS on the resume? Oh yes. As the candidate this is also great when the interviewer says something like “It says here you’ve worked with x” and you go “I’m fairly certain that that wasn’t on there when I submitted the resume (to the recruiter), let me see that” and it turns out like the OP said, extra skill added in a different font.