I am working in a product based company.When I joined the company, there were two large issues with the product.These issues were causing a lot of refunds.The issues were known for about 6 months but nobody knew what was causing the issues.I caught both of these issues and solved which saved my company a lot of refund cases and in turn saved them a lot of money.About one third of the people were asking for refunds.

I don't like to brag and I wouldn't like to come off as a self praiser in the interview.But a lot of seniors have told me that if you have saved your company a lot of time or money then these are huge plus points.

So I was wondering how do I mention this in my interview or resume(if I should even discuss this thing at all)


In the question you say: About one third of the people were asking for refunds.

That is your starting point:

Responsible for a major modification to the product which reduced the number of requests for refunds from 33% to less than 10%

You might add a few details or be prepared to discuss them.

Did you get an award for this? You could use some of the text from the writeup/justification paperwork.

It is hard to say that you were responsible for additional sales, because that was also a result of other changes to the product, or a price change, or additional advertising.

Of course it could be argued that these other changes increased the sales into areas that wouldn't be as likely to trigger a refund request.

  • Also, if they ask for reference, OP could give someone's number that know about those incident well enough. – Walfrat Aug 31 '17 at 12:14

This should be a bullet point in your resume. Example

2010-2012: Company XXX: software developer

  • found two major bugs that saved $250000 yearly in product return cost
  • 2
    what do I do if I don't know how much money I have saved? Obviously the number of people asking for refunds vanished but how do I know how much I have saved? – zzzzz May 24 '13 at 11:11
  • 4
    Ask the person in charge of money. – jcmeloni May 24 '13 at 12:32
  • 1
    @workerBoy you'll have to come up with an estimate - on the lines of how many man-holes are there in new york city? How many total customers were there (for that product), what was the refund % before you fixed the bug. How many of those can be directly attributed to those bugs. What were the total customers after bugs were fixed - how many refunds post bug fix. Whats the estimate cost of each refund (this could be higher than sticker price of product). Now you have a ball park number that you probably saved. – YetAnotherUser May 24 '13 at 12:55
  • 3
    @MrFox I hope you care about more than that. I can find hundreds of trivial bugs each day - when can I get a job? – enderland May 24 '13 at 13:38
  • 1
    @enderland Where did I say trivial? My point is that QA/Dev should not be the ones putting price tags on bugs. If that bullet point said "found and fixed critical bugs under tight deadlines" it would be WAY better than "averted $XYZ cost to the comany" -> Does this person REALLY know how much a given bug costs a company? How? Are they a senior manager in the operations department or are they just throwing crap on the resume hoping to impress people with numbers (it has numbers, it must be true!)? – MrFox May 24 '13 at 13:59

A resume or interview is different from a normal social interaction. A prospective employer is trying to find the best candidate for the job, so a candidate telling them accomplishments is doing them a service by providing more information on which to base the decision. As long as the information is presented in a factual manner, it's not inappropriate to "self praise". Just keep the focus on how the information would help the company, rather than how great it makes you look.

  • 3
    Welcome to the Workplace -- note that this question was answered over 4 years ago. Please take a look at some more recent questions as well that need feedback. – mcknz Aug 30 '17 at 19:45

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .