Oct 11 2010

The Resume is Dead

The resume as you know it is dead. Having a great resume and a perfect cover letter is not enough of a differentiator. Every candidate will have the same alphabet soup of buzzwords and they all list the same excellent communication and interpersonal soft skills in their resume. Any hiring manager will have the same experience of looking at inbox full of resumes that read the same. There is very little scientific method in the hiring process, it’s mostly voodoo. One way passionate candidates distance themselves from apathetic candidates is by learning a new programming language on their own, by contributing to open source projects, and by blogging and teaching what they’ve learned.

Recruiters are constantly looking for top candidates outside the traditional job boards, career fairs, job listings. There have been many instances where coders land job interviews because of their top rated technology blog, or their Stack Overflow reputation, or their side project in GitHub.

Recently, two stories made the front page of Hacker News that demonstrates that working running demonstrable code is better than sending out your static resume.

After Google released it’s Search Instant feature, Stanford student Feross Aboukhadijeh used the publicly available YouTube API to develop YouTube Instant. Feross was contacted by YouTube CEO Chad Hurley and offered a job via a tweet.

Designer Rodrigo Galindez gets hired by Zendesk after posting his thoughts and UI mockup to improve the new Twitter design.

As a candidate, you have to think outside the box, outside the resume. Every candidate will have a nice crisp resume. You can’t possibly distinguish yourself from other candidate by the format, font, or flow of your resume. Where appropriate be sure to highlight your contribution to open source projects, technical blog, of even the small natural language pet project written in scheme you might be tinkering with.


Aug 14 2010

Resume and Interview Tips

I’ve recently had an opportunity to interview for a job opening at my company. From my experience with the interview process, from both sides of the table, I have a few non-technical tips that might be helpful for someone looking for a new challenging position where they will leverage their skills and such and such years of experience in x, y, and z programming languages.

  • Proof read your resume and fix obvious typos, you can’t say you detailed oriented if you have basic spelling errors.
  • I would leave out MS Access 2000 out of technical skills. It’s also not necessary to list HTML, DHTML, and HTML5.
  • Ensure your cover letter or email is in one font, it shouldn’t look like you cut and pasted from somewhere else.
  • The minimum research a candidate needs to do is look up the company website himself prior to interviewing.
  • At a minimum candidate should be able to figure out our URL by a) clicking the link on job description b) from my email.
  • Use a good phone line for a phone interview.
  • Make sure the interviewer gets the feeling that you want to work there, not only that you have the skills to work there.  If you don’t got the skills show enthusiasm, their is always a job for the great candidate, even if they have to rewrite the job description.
  • Don’t name your resume anything but you name, and maybe the word resume  on it.  Don’t put a date geolocation or airport codes, etc.