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?
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.
Comments
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?
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.
Well at some point you can say the same thing of all of them right? Nobody thinks you did this on your own.