A quick thought on reviewing resumes…

with 3 comments

I’ve been reviewing a lot of resumes lately.  Why do developer candidates list all the technologies that they have ever read a blog post about?  Things like this on web and software developer resumes are very common:

.NET (all versions), C#, VB.NET, PHP, Python, Java, HTML, CSS, JavaScript, jQuery, SQL, SQL Server, TSQL, MySQL, PostgreSQL, SQLite, MongoDB, Redis, IIS, Apache, nginx, xUnit, nUnit, RhinoMocks, ninject, StructureMaps, NHibernate, SparkViewEngine, SVN, Git, MVC, ActiveRecord, O/R Mapping, IoC, JSON, BSON, XML, Web Services, Threading, Sockets, TCP, HTTP.

Last summer, when I hired a carpenter to complete the unfinished basement in our house I didn’t ask him to enumerate all the tools he knows how to use:

Hammer, screwdriver (flathead and phillips), drill (including bits), saw, wrenches (imperial and metric)…

Could you imagine trying to hire a carpenter based on this information?  What I need to know was if he could do things like build walls, install flooring, replace windows, repair siding, etc.

My question for you: how could or should candidates write their resumes to be more effective?

Written by scottporad

April 29th, 2010 at 9:24 am

Posted in Cheezburger

«
»

3 Responses to 'A quick thought on reviewing resumes…'

Subscribe to comments with RSS or TrackBack to 'A quick thought on reviewing resumes…'.

  1. Because the résumé has to get through HR first, and they look for keyword matches.

    Jeremy Stein

    29 Apr 10 at 10:26 am

  2. The job search process has been reduced to a set of SQL strings and key words. As far as I see it, candidates are simply doing what they have to to get noticed. There has to be a better way to match supply and demand in a more humane manner…

    Bojmir Revodneb

    29 Apr 10 at 2:39 pm

  3. Writers are not appreciated enough, thank you for taking the time to post this.

    Danny

    26 May 10 at 8:29 am

Leave a Reply