Timeline for How would a developer who mostly fixed bugs for years at a company call out their contributions in their CV?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2019 at 8:49 | vote | accept | Mathematics | ||
| May 21, 2019 at 7:33 | history | edited | Justin | CC BY-SA 4.0 |
Update to provide an alternative to mentioning $$s
|
| S May 21, 2019 at 5:30 | history | suggested | CommunityBot | CC BY-SA 4.0 |
Corrected spelling
|
| May 20, 2019 at 21:05 | comment | added | Chronocidal | Also worth considering: How many of these bugs caused issues that needed regular manual intervention as a workaround? How much time did that take per year/month/week? Enough entries reading "Fixed blah-blah-blah, saving # man-hours per week/month/year", and you could probably convince some HR teams that hiring you is cheaper than not hiring anyone! (Not Accounting through. They should be better with numbers than that) | |
| May 20, 2019 at 18:45 | review | Suggested edits | |||
| S May 21, 2019 at 5:30 | |||||
| May 20, 2019 at 16:46 | comment | added | davidbak | After a contracting job that was maintenance on a legacy production system I emphasized the importance of the system and of minimizing downtime (therefore the value of my contributions) in terms of % of company revenue the production system generated (which was significant) (as well as TPS, size of fleet, and so on to indicate the scale of what I was responsible for). | |
| May 20, 2019 at 12:34 | comment | added | Justin | "Maintained and enhanced...." - Me too. skills to fix bugs - Such as reading other people's code, a greatly underrated skill. "Enhancing" can also mean making the code easier to read (therefore decrease maintenance cost), often done whilst bug fixing. OP, did you ever look at some piece of garbage, and refactor it slightly, a) to fix the bug, b) to improve overall quality? Add that in too; "Refactored to leverage new framework feature X to reduce codebase". | |
| May 20, 2019 at 12:18 | comment | added | Keith | I've got lines in my resume that state "Maintained and enhanced...." whatever website or application I was responsible for. Anyone that interviews for a developer position ought to realize already it takes skills to fix bugs, as well as starting new things from scratch. It's up to you to emphasize that in an interview, and to sell yourself. | |
| May 20, 2019 at 12:15 | comment | added | Justin | There is nothing whatsoever wrong with being the guy that tracks down and resolves issues - Certainly true. I'm primarily a developer, but I just spent the last 2-3 weeks doing exactly this. Some contracts have been nothing but that. | |
| May 20, 2019 at 11:54 | comment | added | Keith | I would add, if the company uses Github or something where the changes are tracked, he should be able to do some sort of reporting to say HOW MUCH he did. There is nothing whatsoever wrong with being the guy that tracks down and resolves issues. | |
| May 20, 2019 at 8:48 | history | answered | Justin | CC BY-SA 4.0 |