News for hackers. Stuff that matters.
Re:Lessons from a year’s worth of hiring data (2013) by ryandrake on Monday August 17, 2015 @07:54PM (#10076843)
I've always thought the best resume format is "Action -> Result" rather than simply listing your responsibilities and/or technical knowledge. People get hired based not on what they did or know, but based on how what they did helped add value to their company.

Example:

    WEAK
    ----
    - Responsible for development and maintenance of the FooBar software suite
    - Skills applied: Java, HTML, CSS, REST APIs

    STRONG
    ----
    - Added BarBuzz feature to FooBar software suite, which contributed to 25% increase in product sales and winning 2 industry awards.
Re:Lessons from a year’s worth of hiring data (2013) by Swizec on Monday August 17, 2015 @08:32PM (#10076984)
I agree, action -> result always sounds more impressive.

But to a point it's always felt disingenuous to me as far as engineering goes. Sure, I implemented the BarBuzz feature. But a marketing person gave the idea, a product person specced it out, a UX person designed it, a UI person made it pretty, and all I did was the final implementation.

Did I really add the feature, or did I just implement it?

Re:Lessons from a year’s worth of hiring data (2013) by ryandrake on Monday August 17, 2015 @08:40PM (#10077006)
Everyone else who touched the feature is going to also say they added it, on their resume. You have as much of a claim to it as they do. Your job title and the size of the company is clear, so the reader can infer the size of your contribution from that.
Re:Lessons from a year’s worth of hiring data (2013) by HaloZero on Tuesday August 18, 2015 @01:33AM (#10077725)
Well at some point you can say the same thing of all of them right? Nobody thinks you did this on your own.