Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

One of things I do in my Resume is try to quantify the impact my work has had in the particular company I was with at the time. The reason is it shows the value my work had added to the business. Is this what you guys do as well or am I the only one?

In my previous job this was easy as I worked on short/medium internal applications and it was fairly easy to measure end result. For example, external consulting company quoted $50,000 for an application Business Services department wanted I completed it in 3 days so I say I saved the company $48,000.

I have been in my current job for 3 years but all of it has been on 1 single well established product. About 30% work is maintenance and 70% work is on new modules. I have worked on various modules like API (WCF), Security (2 factor authentication), etc.

How should I quantify work on modules?

share|improve this question

closed as off-topic by MichaelT, gnat, Corbin March, Robert Harvey, Kilian Foth Sep 2 '13 at 8:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking career or education advice are off topic on Programmers. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most cases, any answer is going to be a subjective opinion that may not take into account all the nuances of a (your) particular circumstance." – MichaelT, gnat, Corbin March, Robert Harvey, Kilian Foth
If this question can be reworded to fit the rules in the help center, please edit the question.

add comment

1 Answer

up vote 9 down vote accepted

You're not the only one. In fact, most resume writing books and articles suggest quantifying results. It helps the reader go beyond your skill set and see the direct benefits you bring to any organization. A few quantifications off the top of my head:

  • Cut maintenance time required by X%.
  • Cut average service response time by X%.
  • Introduced technology X, process X, or technique X, which saved the average developer 15 minutes a day - multiply by 5 developers, 5 days a week...
  • In 6 months of development, bug reports dropped from an average of 10 per week to 5 per week.
  • Implemented feature X, which included all of these important decisions, algorithms, and relationships: ...
  • Mentored peers in technology X which allowed us to do Y.
  • Made an important decision which saved the company X dollars.
  • I did X and this is why that's important: ...
  • Improved group morale because of X, Y, Z.
  • Reduced meeting times from X hours a week to half that.
share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.