4 ms·
There’s a lot of bad advice here. Like you can dismiss this article right when the author says they read every resume and don’t use a scanner. Unless this is a
by jonathankoren 4y ago
There’s a lot of bad advice here. Like you can dismiss this article right when the author says they read every resume and don’t use a scanner. Unless this is a tiny shop with no recruiter anywhere in the process, this simply isnt true. The recruiter is going to screen some of them, even before the hiring manager gets to them.
Now don’t get me wrong. Some of the stuff in the article is good, if tailored for new grads and junior people, but some is just bad and wrong.
I’d say pretty much anything everything billeted in this article is trash. The insights in the prose.
TL;DNR
Don’t skip the keywords folks.
No one gives a fuck about your social media (eg StackOverflow, GitHub, Kaggle, etc). I don’t have time to read some rando’s code, and all it does it show me that you don’t have a hobby outside of promoting yourself on social media.
- zwieback 4y agoWow, so much venom. I wonder what your cover letter/resume looks like.
- jonathankoren 4y agoI’m easy to find. :)
- customaccount 4y agoPlot twist: He has worked at Yahoo, Microsoft, Linkedin, Facebook, Mozilla and Apple
- twitchard 4y agoWrong. I've been a hiring manager at a place with >100 engineers and a recruiting team and - I still read every resume - I ignored the keywords - I pretty much valued exactly what the author does.
- jonathankoren 4y agoIf you're not using the recruiting team to screen the resumes what's the recruiting team even for? Or are you simply not getting resumes?
- SoylentYellow 4y ago> No one gives a fuck about your social media (eg StackOverflow, GitHub, Kaggle, etc) This is just plain wrong. When doing interviews at my previous company, we always looked at their github repo if provided.
- physicsguy 4y agoDo you not find that 95% of the time it's just a blank GitHub though? The only people I've seen without that are either in academia or work on OSS in their day job in some way.
- SoylentYellow 4y agoMy area is tightly coupled to a few OSS projects, so we tend to attract people that are active contributors. I've never been let down in the in-person interview by someone with a strong github resume.
- yamtaddle 4y agoOr bootcamp grads.
- physicsguy 4y agoI look at those but they don’t tell me much as people are often working on a template and have had help, so I can’t disentangle what is someone’s work as easily
- jonathankoren 4y agoSame thing with GitHub activity grid. I don’t even know what it’s supposed to tell. Even if I’m writing code everyday, that doesn’t mean I’m checking it in, and even if I was, I’m not doing it on a public repo or even on a GitHub hosted repo.
- physicsguy 4y agoIt can be gamed too. I remember a thing a long time ago that would make commits to a repository to give it space invaders in the grid!