Timeline for answer to Resume: How to quantify my contributions as a software engineer? by Player One
Current License: CC BY-SA 4.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2019 at 18:35 | comment | added | joojaa | How would a software engineer even quantify customer retention? I mean how do you prove that was actually the thing that did it. I mean you can say customer retention went up when you were working there but we dont know if it was the programmer that caused it. On the otherhand if you do some marketting it is a valid metric to say that it increased while you were there even if theres no proof that was what caused it. | |
| Sep 10, 2019 at 18:20 | comment | added | TheLuckless | Trying to quantify things down into sales or user numbers doesn't really say much about abilities for software development. Breaking things down and highlighting problems solved [And how they possibly lead to those sales or user numbers] seems to tell a lot more in my mind. | |
| Sep 10, 2019 at 8:59 | comment | added | Gregory Currie | Yes, quantify everything doesn't really work when you're part of a team (and I would argue that's true for all professions). | |
| Sep 10, 2019 at 6:33 | history | answered | Player One | CC BY-SA 4.0 |