Evaluating Software Developer Resumes for a Startup

View of the Skiles walk way from the Georgia T...
Image via Wikipedia

Recently my brother asked me for advice about evaluating software developer resumes as his successful Spanish dictionary startup is growing and hiring. The market for software developers is extremely competitive right now as startups and established companies are investing more in their web and mobile apps. A software developer should not be evaluated on her resume alone but it should be a good starting point in the hiring process.

Here are some tips for evaluating software developer resumes for a startup:

  • Try and use the information provided to determine if they are smart and get things done
  • Look for indications they enjoy programming for fun outside of work, like personal projects, open source projects, etc
  • Research their cited Github account or open source projects and find out what they’ve contributed
  • Absent any or little work experience look at the quality of their college education (e.g. Georgia Tech) as well as their overall GPA and major GPA
  • Assess the selectiveness of their current employer as well as length of tenure at past positions (I like to see at least two years at each position, but this is very subjective)

My favorite early indicator of a good software developer is a true passion for coding demonstrated by personal projects outside of work. We still require potential developers to develop custom code during the hiring process, pass a technical assessment, write essays, and, most importantly, fit in our corporate culture. A well done resume gets a software developer in the door, which is only the beginning of the process.

What else? What other things do you look at when evaluating software developer resumes for a startup?

Comments

One response to “Evaluating Software Developer Resumes for a Startup”

  1. Vicki Z Lauter Avatar

    I have noticed as well this year technical folks are getting harder to find. While companies that have openings for any position will look at “qualifications” and “interviews” as a way to determine if someone is right for the role. I recommend companies “benchmark” what a successful developer or marketing person, etc for THEIR organization looks like.

    A solid developer, etc at company A may not be successful at company B. By benchmarking jobs (not people) then assessing your applicants against that benchmark you’ll end up with the right people in the right roles.

Leave a reply to Vicki Z Lauter Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.