1–10 of 23 posts
on my resume do you look at:
my website? my github? my past work experiences, if so do you read the description of what I did? my projects, if so do you read the description of the project? the languages and technologies I know?
All but a handful of recruiters will not because they simply don't understand any of that. They don't understand whats on the resume or job description. Better ones will take note of those things and pass them along to the hiring manager, who should take a look. But it's best if you link them in your resume.
Here's my comprehensive write-up on resumes, I think this is what you are looking for:
http://www.madeupname.com/optimize-developer-career/resume-t...
I do, but I'm an outlier. I have a CS degree and 20 years of software experience, so I'll actually look at your code and if I know that language, take a look at your style. I've seen someone check all her Emacs autosave (~) files into Github. And unnecessarily jam multiple classes into one file. That was a bad sign. All but a handful of recruiters will not because they simply don't understand any of that. They don't…
I do, but I'm an outlier. I have a CS degree and 20 years of software experience, so I'll actually look at your code and if I know that language, take a look at your style. I've seen someone check all her Emacs autosave (~) files into Github. And unnecessarily jam multiple classes into one file. That was a bad sign. All but a handful of recruiters will not because they simply don't understand any of that. They don't…
other than style what else do you look for when you check out a code base?
- your intent: playing around to learn, creating something serious, contributing to OSS, etc.
- how far you got
- who is using it?
- solo or collaboration
- how production ready is this?
I suppose you could sum that up with one question: "Where is this on the spectrum between homework and a real product?"
This falls into the topic of side projects, and I wrote about that in detail here:
My resume is either still out there on some "jobs" web site somewhere or it's been sold/shared between recruiting firms as I still get one or two "cold" e-mails a week from a recruiter; I haven't been "looking" for 5+ years.
In mine, near the beginning, it says something to the effect of "If the responsibilities for your position include the words 'Microsoft' or 'Windows' anywhere, I am not interested in the position. Please do not contact me."
The last recruiter e-mail I received, two days ago, says:
> Your profile came up in my database as a possible candidate that might be qualified for a new Windows Systems Admin I received in my office this morning. My client is with the Department of Defense and is looking for someone with a MSCA [sic] or MCSE or higher for this role.
I believe the overwhelming majority of them don't look at them at all. They punch a keyword or two into their database, then, like spammers, blast the same form e-mail out to anyone whose name comes up.
I do, but I'm an outlier. I have a CS degree and 20 years of software experience, so I'll actually look at your code and if I know that language, take a look at your style. I've seen someone check all her Emacs autosave (~) files into Github. And unnecessarily jam multiple classes into one file. That was a bad sign. All but a handful of recruiters will not because they simply don't understand any of that. They don't…
I'm pretty sure most of them don't. My resume is either still out there on some "jobs" web site somewhere or it's been sold/shared between recruiting firms as I still get one or two "cold" e-mails a week from a recruiter; I haven't been "looking" for 5+ years. In mine, near the beginning, it says something to the effect of "If the responsibilities for your position include the words 'Microsoft' or 'Windows' anywhere,…
You're going to hold off the recruiters who conscientiously scan resumes and take such requests seriously at the expense of triggering automated scans for those keywords. I doubt if it's a net win.
For recruiters who are purely matching using LinkedIn recruiter filters a lot of the matching is done with your skills section and the descriptions under each job.
It's helpful to add industries you want to work with and languages/technologies w/ context. e.g. worked as a javascript developer for X company that did Y, a leader in the Z industry. built end-to-end messaging system using javascript and socket.io that had an engagement with 30k users.
This will help you get more relevant matches. Granted you'll get some spam- but there are some quick tricks like asking for e-mails to include certain information on your LinkedIn description so you can easily filter out.
As a software eng. who's getting to see both sides of the market it's always best to get a referral to a really good agency in your location. A good recruiter is worth a lot of time/money especially for such an important decision like where you're going to be spending 1/4~ of your week at.
Whenever we interview a candidate, we actually try to learn as much about people based on what they have online.
Before we set up an interview, we usually check out their personal site, their Github/Bitbucket/etc, any sites related to those repos, their Linkedin, Twitter, etc, etc...
We try not to be too creepy, but we just really want to be somewhat familiar with their work before they come in.
So far there's a 1:1 correlation between viewing my website and sending me a non-automated LinkedIn message.